SOLVED Server Outage ETA: 6 PM EDT

wardmundy

Nerd Uno
Joined
Oct 12, 2007
Messages
15,385
Reaction score
2,728
fsck is a 2-3 hour process. In the meantime...

Be advised, this negatively affects logins to Incredible PBX servers which depend upon incrediblepbx.com to run pbxstatus and Automatic Update Utility. Ctrl-C is your friend. :)

If you get in a crunch for something, these sites still work:

Incredible PBX: http://incrediblepbx.impact.wardmundy.net/

Nerd Vittles: http://new.nerdvittles.com/

Downloads still work with FQDN adjustments above. Not the best time to attempt a new install. :aureola:
 
Last edited:

wardmundy

Nerd Uno
Joined
Oct 12, 2007
Messages
15,385
Reaction score
2,728
You can edit /usr/local/sbin/pbxstatus and replace the first _PUBLIC line with the following to get back in operation:
Code:
    _PUBLIC=""
    _PUBLIC="Public Info: `curl -s -S --user-agent "Mozilla/4.0" --connect-timeout 2 http://myip.incrediblepbx.com | awk 'NR==2'`"
   if [[ `echo ${#_PUBLIC}` = "13" ]]; then
    _PUBLIC="Public Info: `curl -s -S --user-agent "Mozilla/4.0" --connect-timeout 2 http://incrediblepbx.impact.wardmundy.net/myip/ | awk 'NR==2'`"
   fi
 
Last edited:

wardmundy

Nerd Uno
Joined
Oct 12, 2007
Messages
15,385
Reaction score
2,728
Update #2 09.12.2019 15:11. Manual FSCK (file system check & repair) is still running across all SSD disks. It seems that primary SSD drive has inconsistency errors. Those should be fixed by FSCK in a few hours. Local backup drive on the server with recent, 09/10 backups is not affected.

Update #1 09.12.2019 14:25. Server got stuck with "inconsistency" errors. It has been rebooted with manual FSCK (file system check). It normally takes 2-3 hours.
 

Members online

PIAF 5 - Powered by 3CX

Forum statistics

Threads
22,560
Messages
138,834
Members
14,669
Latest member
cleron