Hi,

I am running a SEPM RU5 on a Windows Server 2012 machine. I created a SEP 12.1.5337.5000 installation package for Linux clients using the SEPM and installed it on a RHEL machine. The installation was fine. However the client just can't connect to the management server.  It shows the server status as Offline. The Linux client also does not show up in the SEPM's list of clients.

I followed the instructions at Enabling Sylink logging for the Symantec Endpoint Protection client for Linux to set up logging and noticed that it complains about "registration request returned error 500". When i looked at scm-server-0.log file on the SEPM machine, it has a "SEVERE error: java.lang.NumberFormatException: This is not an valid IP address." I just can't figure out what's the error as both machines are able to ping each other.

Any help is greatly appreciated!  Thank you.

Did you replace the sylink file? There are steps at this link:

http://www.symantec.com/docs/HOWTO109623

can you post the sylink log please?

Check the symantec article for solve it

500 INTERNAL SERVER ERROR clients are not able to register with the Symantec Endpoint Protection Manager

"Failed to connect to the server" or "Error 1069" after upgrading to Endpoint Protection Manager 12.1.5

Hi there,

I've tried it and its still not working.

Hi there,

the solutions did not work for me.

I did not install IIS on the server and the services are already added to  the security settings as mentioned in the second article. I'm still getting the same error.

Hi ,

I'm unable to post the logs as the machines are on a secured network. The logs on the SEPM machine basically just says that the IP address is invalid. It did not specify what was the invalid value provided (making it harder to debug) even though the log level has been set to FINEST.

The sylink log prints the xml data that it was sending to SEPM for registration followed by:

ERROR request.POST Registration request returned error 500

WARN cve.heartbeat Failed to connect to server:  HTTP://<hostname>:<port>

... the rest of the log messages are repetitive.

Are there other ways to log more data for debugging especially at the SEPM side?

can you check if your linux server can reach SEPM on port 8014?

might be a firewall in between which is blocking the connection

Hi,

there isn't any firewall in between.

I'm having the same issue too, I can telnet to to the SEPM by using the following command telnet SEPMIP 8014 and telnet SEPMIP 443

I have three RHEL6 servers on the same subnet and one of them can connect to the SEPM but two others can't

I have checked the logs and it shows as connecting to different regional SEPM's but then when i check the console on SEPM that the log says it connected earlier to it is showing as offline

 I've replaced the sylink file and still have the same issue

Here is the issue:

I would say you are using the un-supported Distro and Kernel.

Issue reported: SEP For Linux clients are not communicating with SEPM (12.1 RU5)

Reviewing the secreg logs and Sylink logs reveals that Linux client is not able to register with SEPM.

Snip in from secreg log:

5/05 08:30:31 [2640:4380] 10.xx.xxx.xxx<AgentInfo AgentType="105" PreferredMode="1" DomainID="xxxxxxxxxxxxxxxxxxxxxxx" UserDomain="" LoginUser="" ComputerDomain="(none)" ComputerName="xxxxxxxxxx" PreferredGroup="My%20Company%xxxxxxxxx%xxxxxxxx%5cxxx%5cxxxx" HardwareKey="843B9F87E47DBBAE607D0BEA5A84AB8D"/>--FAILED

05/05 08:30:31 [2640:4380] 5 Server returned: 500 Internal Server Error

Snip from Sylink log:

2015-04-22T05:21:55.793CDT -225453200 ERROR request.post Registration request returned error 500

2015-04-22T05:21:55.793CDT -225453200 WARN cve.heartbeat Failed to connect to server: HTTP://10.xx.xxx.xx:8014

After reviewing the logs what I have found that customer is using unsupported Kernel for the update patch. (In this case it’s Distro: CentOS release 6.6 (Final) Kernel: 2.6.32-358.11.1.el6.x86_64)

Reference: http://www.symantec.com/docs/TECH223240

I did reproduce the issue with unsupported Kernel version in our test lab and found the same results as above. (Un-supportedDistro:Centos 7 (Kernel:3.10.0-123.4.4.el7.x86_64) and Ubuntu 14.04 (Kernel: 3.11.0-15-generic))

I re-tested this with Centos 6.5 (kernel: 2.6.32-431.el6.x86_64) which is supported and it worked without issue.

Hi there,

I had the exact issue ""SEVERE error: java.lang.NumberFormatException: This is not an valid IP address." and with some help from Symantec Support we found out that it was because I didn't have a default gateway. (I had a route so I could get to the SEPM server)

I have not completed the testing but I added a GATEWAY=xxx.xxx.xxx.xxx in /etc/sysconfig/network-scripts/ifcfg-<interface> and gave it a reboot and it seems to have sprung into life (you might just be able to restart that interface).

HTH

Tim