[SOLVED] Screenconnect - Stopped Working
-
@anonymous said:
Crap, can someone move this....
Moved.
-
CentOS logs are in /var/logs/messages
At least most logs are. /var/logs is the logging directory. Nearly everything goes into the "messages" catch all. But there are specific logs too for NginX, Apache (HTTPD), ScreenConnect, etc.
-
Do you know what time the SC app stopped working?
-
-
Oh boy, that's a big window for log scouring. I assume that there was no reboot during that time? Do you have sar collecting data? That might help to pinpoint when things changed.
-
When I was running Screen Connect on Linux it would fail on occasion like this and I would just download the Tar file and reinstall over the top and it would usually get it going again.
https://www.screenconnect.com/Download -
@scottalanmiller said:
Oh boy, that's a big window for log scouring. I assume that there was no reboot during that time? Do you have sar collecting data? That might help to pinpoint when things changed.
Darn it.... Forgot to turn on sar
-
@scottalanmiller Rebooted Monday.
-
@anonymous said:
@scottalanmiller said:
Oh boy, that's a big window for log scouring. I assume that there was no reboot during that time? Do you have sar collecting data? That might help to pinpoint when things changed.
Darn it.... Forgot to turn on sar
yum -y install sysstat -
@GregoryHall said:
When I was running Screen Connect on Linux it would fail on occasion like this and I would just download the Tar file and reinstall over the top and it would usually get it going again.
https://www.screenconnect.com/DownloadDefine "on occasion" for me. I really want to get mine off the Windows box it is on and on a Linux based (likely CentOS 7) VM.
-
@JaredBusch said:
Define "on occasion" for me. I really want to get mine off the Windows box it is on and on a Linux based (likely CentOS 7) VM.
Yes, please do! Also, do you recommend windows instead of linux? If so, Why?
-
@anonymous said:
@JaredBusch said:
Define "on occasion" for me. I really want to get mine off the Windows box it is on and on a Linux based (likely CentOS 7) VM.
Yes, please do! Also, do you recommend windows instead of linux? If so, Why?
Keep in mind he's a full time Windows engineer that doesn't use Linux.
-
@scottalanmiller said:
Keep in mind he's a full time Windows engineer that doesn't use Linux.
Sadly, for the most part I am too. Trying to break into linux but.....
-
Finding issues like this and pushing through to find answers is a great way to learn a lot about it quickly.
-
@scottalanmiller said:
Finding issues like this and pushing through to find answers is a great way to learn a lot about it quickly.
That's why I haven't given up yet!
-
@scottalanmiller said:
CentOS logs are in /var/logs/messages
At least most logs are. /var/logs is the logging directory. Nearly everything goes into the "messages" catch all. But there are specific logs too for NginX, Apache (HTTPD), ScreenConnect, etc.
Both Directorys are missing? WTF?
-
@scottalanmiller said:
Keep in mind he's a full time Windows engineer that doesn't use Linux.
irrelevant though to reporting back the definition of "on occasion" as it pertains to the controller in question.
-
[root@screenconnect ~]# cd /var/logs/messages
-bash: cd: /var/logs/messages: No such file or directory
[root@screenconnect ~]# cd /var/logs
-bash: cd: /var/logs: No such file or directory -
@anonymous said:
@scottalanmiller said:
CentOS logs are in /var/logs/messages
At least most logs are. /var/logs is the logging directory. Nearly everything goes into the "messages" catch all. But there are specific logs too for NginX, Apache (HTTPD), ScreenConnect, etc.
Both Directorys are missing? WTF?
That's EXTREMELY odd. There is no /var/log at all?
Sorry, I typod. /var/log not logs
-
Output:
[root@screenconnect ~]# ls /var/log anaconda grubby secure audit lastlog secure-20150802 boot.log maillog secure-20150809 btmp maillog-20150802 spooler btmp-20150801 maillog-20150809 spooler-20150802 cloud-init.log messages spooler-20150809 cloud-init-output.log messages-20150802 tallylog cron messages-20150809 tuned cron-20150802 ppp wtmp cron-20150809 sa yum.log dmesg screenconnect dmesg.old screenconnect-1227cf7eaca84600 [root@screenconnect ~]#
