Koozali.org: home of the SME Server

Obsolete Releases => SME Server 9.x => Topic started by: ElFroggio on June 14, 2017, 05:08:19 PM

Title: signal-event post-upgrade; signal-event reboot;exit
Post by: ElFroggio on June 14, 2017, 05:08:19 PM
Hi,

SME 9.2

To update, I do an ssh, then yum update and after the update, I use:

Code: [Select]
signal-event post-upgrade; signal-event reboot;exit
It supposed to close my session and restart the server. Until 9.2 it worked. The last couple of 9.2 updates, it didn't and today with the qsmtp update, I checked what I was doing.


I had to get to the console, (swap the monitor cables to have the server screen), alt-ctrl-del to restart the server.

Something as changed. What should I do differently?

Thanks

Syv

Title: Re: signal-event post-upgrade; signal-event reboot;exit
Post by: Stefano on June 14, 2017, 05:10:21 PM
Nothing changed
I had similar issues in the last but they were temporary
Title: Re: signal-event post-upgrade; signal-event reboot;exit
Post by: ElFroggio on June 14, 2017, 05:18:35 PM
Hi,

Does this mean that I will need to reboot from the console for every update?

Thanks

Syv
Title: Re: signal-event post-upgrade; signal-event reboot;exit
Post by: Daniel B. on June 14, 2017, 05:37:29 PM
Quote from: ElFroggio on June 14, 2017, 05:08:19 PM
  • It doesn't work anymore.

This doesn't help us to help you. What's happening ?
Quote from: ElFroggio on June 14, 2017, 05:08:19 PM
  • Doing a reconfigure through the web interface doesn't restart the server anymore
That's expected, the configuration console only reboot the server if needed, when you have changed some settings
Title: Re: signal-event post-upgrade; signal-event reboot;exit
Post by: Jean-Philippe Pialasse on June 14, 2017, 05:41:16 PM
I would suspect some customization to prevent the reboot to occurs.

personnaly I had no problem with the  following on SME9
Code: [Select]
signal-event post-upgrade; signal-event reboot;exit
To note with SME10 you will not need to add the exit, sshd will kick you cleanly before rebooting.
Title: Re: signal-event post-upgrade; signal-event reboot;exit
Post by: ElFroggio on June 14, 2017, 06:27:56 PM
Quote from: Daniel B. on June 14, 2017, 05:37:29 PM
This doesn't help us to help you. What's happening ?That's expected, the configuration console only reboot the server if needed, when you have changed some settings

I don't know what's happening. Which log should I check?

Quote
I would suspect some customization to prevent the reboot to occurs.

I don't remember any new customization, at least for the last 6 month. Where can I check?

Thanks

Syv
Title: Re: signal-event post-upgrade; signal-event reboot;exit
Post by: Daniel B. on June 14, 2017, 06:29:30 PM
Well, tell us what happens when you run those commands. Maybe it doesn't do anything visible (in which case you should have a look at your logs). But all we know for now is that "it doesn't work"
Title: Re: signal-event post-upgrade; signal-event reboot;exit
Post by: Jean-Philippe Pialasse on June 14, 2017, 06:53:15 PM
/var/log/messages is the log to check

instead of it does not work.
- what did you do ? "signal-event post-upgrade; signal-event reboot;exit" after update via ssh (correct?)
- what did you expect ?
- what did you obtain or saw ?
- have you tried without the ";exit" ?
Title: Re: signal-event post-upgrade; signal-event reboot;exit
Post by: CharlieBrady on June 14, 2017, 10:29:14 PM
Quote from: Jean-Philippe Pialasse on June 14, 2017, 06:53:15 PM
- have you tried without the ";exit" ?

That shouldn't make any difference.

OP can investigate further by just doing "signal-event reboot" and reporting what he/she sees.
Title: Re: signal-event post-upgrade; signal-event reboot;exit
Post by: TerryF on June 15, 2017, 01:00:53 AM
Two sme9.2 servers, one a clean install and latest updates, other updated from sme9.1 and latest updates

Minimal contribs

signal-event post-upgrade; signal-event reboot;exit

Both react as expected.
Title: Re: signal-event post-upgrade; signal-event reboot;exit
Post by: janet on June 15, 2017, 01:25:06 AM
Syv

Quote
OP can investigate further by just doing "signal-event reboot" and reporting what he/she sees.

OP can also include the path eg
/sbin/e-smith/signal-event reboot

& report back here the outcome