...Thanks, it is good to know :)
...
El mar, 02-02-2021 a las 15:01 +0700, Maxim Solodovnik escribió:
> You can use
> `sudo update-rc.d tomcat3 defaults`
> instead of manual link creation :)
>
> On Tue, 2 Feb 2021 at 02:10, wrote:
> > Hello,
> >
> &
You can use
`sudo update-rc.d tomcat3 defaults`
instead of manual link creation :)
On Tue, 2 Feb 2021 at 02:10, wrote:
> Hello,
>
> Thanks - is that the best way? I think a best practice is to add
> --restart unless-stopped to your tutorial docker run command so it
> looks l
20:34, Alvaro a écrit :
For docker:
sudo systemctl enable docker.service
...and for kms you can add it in the script we
made. Then the script will look so:
#!/bin/bash
docker start kms
/etc/init.d/tomcat3 start
...am thinking you are in Ubuntu 20.04 ???
..
El lun, 01-02-2021 a l
For docker:
sudo systemctl enable docker.service
...and for kms you can add it in the script we
made. Then the script will look so:
#!/bin/bash
docker start kms
/etc/init.d/tomcat3 start
...am thinking you are in Ubuntu 20.04 ???
..
El lun, 01-02-2021 a las 19:07 +
Hi Ed,
It i do to run OpenMeetings when turn on the machine
or reboot it is:
sudo nano /etc/init.d/boot
...paste the 2 following lines:
#!/bin/bash
/etc/init.d/tomcat3 start
...push Ctrl+X, will ask to save then press Y,
and Enter to exit nano editor.
Now give execution permission to this
Hello,
Does anyone have a best practice for autostarting kms inside docker
whenever there is a docker or server restart?
Could you share it please?
Also, for tomcat3 to restart automatically on reboot I had to add the
following symlinks:
ln -s /etc/init.d/tomcat3 /etc/rc0.d/K01tomcat3
ln
he purpose of this file listed here? Is it useful?
>>
>>
>> https://cwiki.apache.org/confluence/download/attachments/27838216/tomcat3?version=4&modificationDate=1587657779000&api=v2
>>
>> Thanks,
>>
>> Tom
>>
>>
>>
--
Best regards,
Maxim
Now, I understand where this is used. Thanks
On Thu, May 14, 2020 at 4:23 PM Tom Luo wrote:
> Hi, all,
>
> What is the purpose of this file listed here? Is it useful?
>
>
> https://cwiki.apache.org/confluence/download/attachments/27838216/tomcat3?version=4&modificationDat
Hi, all,
What is the purpose of this file listed here? Is it useful?
https://cwiki.apache.org/confluence/download/attachments/27838216/tomcat3?version=4&modificationDate=1587657779000&api=v2
Thanks,
Tom
;> ExecutorService 'taskExecutor' INFO 03-14 15:54:40.406
>>>> o.k.j.c.JsonRpcClientNettyWebSocket:191 [rbeatExec-e1-t0] -
>>>> [KurentoClient] Connecting native client INFO 03-14 15:54:40.409
>>>> o.k.j.c.JsonRpcClientNettyWebSocket:220
of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' -
with 10 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
support persistence. and is not clustered.
port is not firewalles - neither is 5443.
Any idea what to
KurentoClient] Error sending heartbeat to server. Exception:
>>> [KurentoClient] Exception connecting to WebSocket server
>>> ws://127.0.0.1:/kurento <http://127.0.0.1:/kurento> INFO 03-14
>>> 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:191 [main] -
mpleThreadPool' - with
10 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
support persistence. and is not clustered.
port is not firewalles - neither is 5443.
Any idea what to do to start KMS on buster - tomcat3 is running fine -
this is 5.0.0 M3 adn
er of type: class
>> org.quartz.core.SchedulerSignalerImpl
>> INFO 03-14 15:54:40.716 o.q.c.QuartzScheduler:229 [main] - Quartz
>> Scheduler v.2.3.2 created.
>> INFO 03-14 15:54:40.717 o.q.s.RAMJobStore:155 [main] - RAMJobStore
>> initialized.
>> INFO 03-14 15:54:40.717 o.q.c.QuartzScheduler:294 [main] -
>> Scheduler meta-data: Quartz Scheduler (v2.3.2)
>> 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' with
>> instanceId 'NON_CLUSTERED'
>> Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
>> NOT STARTED.
>> Currently in standby mode.
>> Number of jobs executed: 0
>> Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10
>> threads.
>> Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
>> support persistence. and is not clustered.
>>
>> port is not firewalles - neither is 5443.
>>
>> Any idea what to do to start KMS on buster - tomcat3 is running fine -
>> this is 5.0.0 M3 adn I want to install M4 very soon.
>>
>> Thanks for any ideas or help
>>
>> Ed
>>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
>
--
WBR
Maxim aka solomax
'org.quartz.simpl.RAMJobStore' - which does not
support persistence. and is not clustered.
port is not firewalles - neither is 5443.
Any idea what to do to start KMS on buster - tomcat3 is running fine -
this is 5.0.0 M3 adn I want to install M4 very soon.
Thanks for any ideas or help
Ed
--
WBR
Maxim aka solomax
Links:
--
[1] http://server1.searchy.biz
.quartz.core.QuartzScheduler' - running locally.
> NOT STARTED.
> Currently in standby mode.
> Number of jobs executed: 0
> Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10
> threads.
> Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
> support persistence. and is not clustered.
>
> port is not firewalles - neither is 5443.
>
> Any idea what to do to start KMS on buster - tomcat3 is running fine -
> this is 5.0.0 M3 adn I want to install M4 very soon.
>
> Thanks for any ideas or help
>
> Ed
>
--
WBR
Maxim aka solomax
lly.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
support persistence. and is not clustered.
por
17 matches
Mail list logo
