Are you using the default systemd script in OpenSIPS[1].

[1] https://github.com/OpenSIPS/opensips/blob/master/packaging/redhat_fedora/opensips.service

Best regards,

Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 1/18/23 13:40, Stefan Tobé wrote:
Hi,
I have an issue with Centos 7 running Opensips 3.2

*problem: *
Opensips is restarting 1:30 min after
the following command:
#sudo systemctl restart opensips

note: note: In between this interval  the server works fine


*logs*:
I keep observing these logs every 1:30 min exactly in /var/log/messages:


Jan 18 12:35:36 pmnlscscf02 opensips: Jan 18 12:35:35 [25370] DBG:db_mysql:db_mysql_connect: server version is 10.6.8-MariaDB-1:10.6.8+maria~focal-log Jan 18 12:35:36 pmnlscscf02 opensips: Jan 18 12:35:35 [25370] DBG:core:db_do_init: connection 0x7f479264b5a8 inserted in pool as 0x7f479264b870 Jan 18 12:35:36 pmnlscscf02 opensips: Jan 18 12:35:35 [25370] DBG:core:init_mod_child: type=CHILD, rank=7, module=rest_client Jan 18 12:35:36 pmnlscscf02 opensips: Jan 18 12:35:35 [25370] DBG:core:init_mod_child: type=CHILD, rank=7, module=json Jan 18 12:35:36 pmnlscscf02 opensips: Jan 18 12:35:35 [25370] DBG:core:init_mod_child: type=CHILD, rank=7, module=cachedb_local *Jan 18 12:37:05 pmnlscscf02 systemd: opensips.service start operation timed out. Terminating. Jan 18 12:37:05 pmnlscscf02 opensips: Jan 18 12:37:05 [25359] DBG:core:handle_sigs: SIGTERM received, program terminates *Jan 18 12:37:05 pmnlscscf02 opensips: Jan 18 12:37:05 [25359] DBG:core:shutdown_opensips: Asking process 1 [MI FIFO] to terminate Jan 18 12:37:05 pmnlscscf02 opensips: Jan 18 12:37:05 [25359] DBG:core:shutdown_opensips: Asking process 4 [SIP receiver udp:10.130.2.141:5062 <http://10.130.2.141:5062>] to terminate Jan 18 12:37:05 pmnlscscf02 opensips: Jan 18 12:37:05 [25359] DBG:core:shutdown_opensips: Asking process 5 [SIP receiver udp:10.130.2.141:5062 <http://10.130.2.141:5062>] to terminate Jan 18 12:37:05 pmnlscscf02 opensips: Jan 18 12:37:05 [25368] INFO:core:sig_usr: signal 15 received Jan 18 12:37:05 pmnlscscf02 opensips: Jan 18 12:37:05 [25359] DBG:core:shutdown_opensips: Asking process 6 [SIP receiver udp:10.130.2.141:5062 <http://10.130.2.141:5062>] to terminate Jan 18 12:37:05 pmnlscscf02 opensips: Jan 18 12:37:05 [25359] DBG:core:shutdown_opensips: Asking process 7 [SIP receiver udp:10.130.2.141:5062 <http://10.130.2.141:5062>] to terminate Jan 18 12:37:05 pmnlscscf02 opensips: Jan 18 12:37:05 [25359] DBG:core:shutdown_opensips: Asking process 8 [TCP receiver] to terminate Jan 18 12:37:05 pmnlscscf02 opensips: Jan 18 12:37:05 [25359] DBG:core:shutdown_opensips: Asking process 9 [TCP receiver] to terminate Jan 18 12:37:05 pmnlscscf02 opensips: Jan 18 12:37:05 [25359] DBG:core:shutdown_opensips: Asking process 10 [Timer handler] to terminate Jan 18 12:37:05 pmnlscscf02 opensips: Jan 18 12:37:05 [25359] DBG:core:shutdown_opensips: Asking process 11 [TCP main] to terminate
Jan 18 12:37:05 pmnlscscf02 opensips: Listening on

*analysis*:
can it have something to do with process forking and default Centos 7 1:30 min timeout in systemd?


--
mvg
Stefan Tobé


PM Factory B.V.
Bolderweg 2
1332 AT Almere
tel: 06 21 26 59 68
email: [email protected] <mailto:[email protected]>
PGP public key: click here to download <https://drive.google.com/file/d/1yiFSid3_Etq0rmdjQbB_q4s7-2KXiy71/view?usp=sharing>

<http://www.privatemobility.nl>

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to