[SOLVED] Screenconnect - Stopped Working

Alex Sage

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?

JaredBusch

@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.

Alex Sage

[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

scottalanmiller

@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

Alex Sage

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 ~]#

Alex Sage

This maybe?
/etc/rc.d/init.d/screenconnect-1227cf7eaca84600: line 109: java: command not found

scottalanmiller

So you have messages for most things and screenconnect for specific stuff. I'd start with those two.

scottalanmiller

@anonymous said:

This maybe?
/etc/rc.d/init.d/screenconnect-1227cf7eaca84600: line 109: java: command not found

That could do it. Do this...

find / -name java

Alex Sage

[root@screenconnect log]# find / -name java
/etc/pki/java
/etc/pki/ca-trust/extracted/java
[root@screenconnect log]#

scottalanmiller

Looks like Java is missing. No idea how that happened.

dafyre

@scottalanmiller Security update? lol.

scottalanmiller

Well you can't argue that Java isn't a lot more secure now!

scottalanmiller

I would start here and see if this works...

yum -y install java

Let's experiment. This will install the open source Java replacement that Red Hat ships natively.

Alex Sage

WTF. The server was working fine the whole time!

DNS was updated by mistake.....

Boy do I feel silly.

scottalanmiller

LOL. It's generally the simplest things that get us

Alex Sage

I went to the IP, and working fine.... So I was like hmmmmmmmmm.

Alex Sage

So should I remove Java now?

scottalanmiller

Yes, you should remove it.

scottalanmiller

Sadly, renaming the thread after the title has been posted breaks links to the threads. That is something that we wish NodeBB would address.

Alex Sage

@scottalanmiller And reboot? or is that the windows admin in me? =P