What Are You Doing Right Now
-
@brandon220 isn't the automagically "sudo reboot now". . .
-
@dustinb3403 said in What Are You Doing Right Now:
@brandon220 isn't the automagically "sudo reboot now". . .
reboot
does not require a parameter. It will do it immediately by default. -
@scottalanmiller said in What Are You Doing Right Now:
I've got customer reporting that hosted Spiceworks helpdesk is down. I see the same thing here. Anyone else seeing this?
Just came back up.
-
@jaredbusch said in What Are You Doing Right Now:
@brandon220 said in What Are You Doing Right Now:
Does anyone have a trick to make FreePBX re-register the voip.ms SIP trunks after an internet outage restores? A cut fiber caused an outage for a few hours yesterday eve. When it was restored, I had to manually get them to register by re-booting the system. I probably could have just disabled and then enabled the trunks for the same result. Seems like it should do this "automagically"....
systemctl restart asterisk
Or...
fwconsole restart
-
@dustinb3403 said in What Are You Doing Right Now:
@brandon220 isn't the automagically "sudo reboot now". . .
Are you thinking of
shutdown -h now
? -
@obsolesce said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@brandon220 isn't the automagically "sudo reboot now". . .
Are you thinking of
shutdown -h now
?It's just force of habit, as I often stand up a system for a one off test, and just don't care to wait for it to shutdown.
Out of habit I just also add the now parameter.
-
@dustinb3403 said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@brandon220 isn't the automagically "sudo reboot now". . .
Are you thinking of
shutdown -h now
?It's just force of habit, as I often stand up a system for a one off test, and just don't care to wait for it to shutdown.
Out of habit I just also add the now parameter.
I guess technically if you want the logs to be 100% accurate wiht a PowerOFF, you'd use
-P
instead of-h
. -
@scottalanmiller said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
I've got customer reporting that hosted Spiceworks helpdesk is down. I see the same thing here. Anyone else seeing this?
Just came back up.
Spoke too soon, definitely not back up.
-
@eddiejennings said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
I've got customer reporting that hosted Spiceworks helpdesk is down. I see the same thing here. Anyone else seeing this?
Looks like something is
updown: https://status.spiceworks.com/No issues with our osTicket.
-
@scottalanmiller you can't really compare a platform that you host and operate yourself versus what does which is likely running on a physical server from 1990. . .
-
@jaredbusch said in What Are You Doing Right Now:
@brandon220 said in What Are You Doing Right Now:
Does anyone have a trick to make FreePBX re-register the voip.ms SIP trunks after an internet outage restores? A cut fiber caused an outage for a few hours yesterday eve. When it was restored, I had to manually get them to register by re-booting the system. I probably could have just disabled and then enabled the trunks for the same result. Seems like it should do this "automagically"....
systemctl restart asterisk
This doesn't solve the problem the OP was asking for - "automagically" - i.e. why is manual intervention required at all? why isn't FreePBX auto reregistering say, ever 1 min or so?
-
@dashrender said in What Are You Doing Right Now:
@jaredbusch said in What Are You Doing Right Now:
@brandon220 said in What Are You Doing Right Now:
Does anyone have a trick to make FreePBX re-register the voip.ms SIP trunks after an internet outage restores? A cut fiber caused an outage for a few hours yesterday eve. When it was restored, I had to manually get them to register by re-booting the system. I probably could have just disabled and then enabled the trunks for the same result. Seems like it should do this "automagically"....
systemctl restart asterisk
This doesn't solve the problem the OP was asking for - "automagically" - i.e. why is manual intervention required at all? why isn't FreePBX auto reregistering say, ever 1 min or so?
If I had a log of the event, I could give more information.
-
@dashrender That's what I really meant... Seems like it should re-connect as soon as service is restored. Luckily it does not happen often.
-
@jaredbusch I did't look at the logs. Just did a restart and calls started flowing.
-
@brandon220 said in What Are You Doing Right Now:
@jaredbusch I did't look at the logs. Just did a restart and calls started flowing.
go get the log file from the time of the even.
ls -l /var/log/asterisk/full*
get that copied local. and then search for your trunk.
-
@brandon220 files are roated in the middle of the morning. So if it happened yesterday it would be in the
full-20180515
file.[jbusch@fpbx ~]$ sudo ls -l /var/log/asterisk/full* [sudo] password for jbusch: -rw-r----- 1 asterisk asterisk 562172 May 15 12:18 /var/log/asterisk/full -rw-r----- 1 asterisk asterisk 2198861 May 9 06:25 /var/log/asterisk/full-20180509 -rw-r----- 1 asterisk asterisk 2143958 May 10 03:37 /var/log/asterisk/full-20180510 -rw-r----- 1 asterisk asterisk 2405220 May 11 05:44 /var/log/asterisk/full-20180511 -rw-r----- 1 asterisk asterisk 1796527 May 12 03:40 /var/log/asterisk/full-20180512 -rw-r----- 1 asterisk asterisk 39681 May 13 03:49 /var/log/asterisk/full-20180513 -rw-r----- 1 asterisk asterisk 480162 May 14 07:42 /var/log/asterisk/full-20180514 -rw-r----- 1 asterisk asterisk 1986362 May 15 03:42 /var/log/asterisk/full-20180515
-
Just got UrBackup up and running at a clients location. Preparing to move them from an old legacy server to a Samba 4 domain on Fedora.
-
@penguinwrangler said in What Are You Doing Right Now:
Just got UrBackup up and running at a clients location. Preparing to move them from an old legacy server to a Samba 4 domain on Fedora.
It's nice, I like it.
-
Windows Admin Center is pretty nice, we are using it at a client now for management and so far, so good.
-
@scottalanmiller Yes it got an update shortly after release which seems to have fixed any problems i had with it like not being able to remove bad computer names from its list of managed computers.