Upgrade went bad

Hi all,

I attempted to upgrade from 2.210.62-7 to 2.210.62-100 as I have done in the past.

I got to:

UPGRADE 100% COMPLETED
REBOOT YOUR BOX NOW FOR NEW KERNEL…

upon reboot, asterisk is stuck in a loop with:

/usr/sbin/safe_asterisk: line 145: 9774 Segmentation fault (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} > /dev/${TTY} 2>&1 < /dev/${TTY} Asterisk ended with exit status 139 Asterisk exited on signal 11. Automatically restarting Asterisk.

so I used

killall -9 safe_asterisk
killall -9 asterisk

to stop the looping. My intention was to reinstall the upgrade but I seem to have no network connectivity. Ping requests (to the gateway IP) time out. Network restart doesn’t help

/var/log/asterisk/full doesn’t reveal anything obvious (to me at least)

Not sure what to do next and looking for some guidance.

Thanks so much!

Did you go from 2.210.62-7 straight to 2.210.62-100 without running the upgrades in between? It’s not clear from your post.

dcitelecom - thanks for looking!

Yes, I did, but don’t see any steps in between I missed.

According to Sangoma Documentation there is nothing in-between.

2.210.62-1- Click on link for full release notes. 2.210.62-2- Click on link for full release notes. 2.210.62-3- Click on link for full release notes. 2.210.62-4- Click on link for full release notes. 2.210.62-5- Click on link for full release notes. 2.210.62-6- Click on link for full release notes. 2.210.62-7- Click on link for full release notes. 2.210.62-100- Click on link for full release notes. This will take your 2.210.62 version system to a 3.211.63-7 version and track.

Sorry. I just assumed you had skipped something.
Maybe check /var/log/messages for errors since this problem apparently affects the entire system?

Good thought…
This is where things begin to go wrong

Feb 17 06:39:36 white-ff6de97e2 apcupsd[1085]: apcupsd FATAL ERROR in smartsetup.c at line 172#012PANIC! Cannot communicate with UPS via serial port.#012Please make sure the port specified on the DEVICE directive is correct,#012and that$
Feb 17 06:39:36 white-ff6de97e2 apcupsd[1085]: apcupsd error shutdown completed
Feb 17 06:39:47 white-ff6de97e2 kernel: asterisk[1386]: segfault at a ip 080d217a sp bf81efa0 error 4 in asterisk[8048000+1bd000]

have to dig further, thanks!