I am currently having a problem with our Zenworks 2017 update 4 Primary (and only) server where the diagnostics are not working at all, the status simply says “server not reachable” it has been like that for a while but everything else seemed to be working perfectly, so sadly fixing this took a bit of a back seat.
I am now trying to fix it, I have tried to remove and then redeploy the probe on the server (I got the msi from the ZENworks_17.4.0_Update.zip) and I am still receiving the same problem.
Does anyone have any ideas on how I can fix this?
I want to upgrade our server to 2020 soon but would like to get this fixed first.
Any help is very much appreciated.
Try this TID and see if the errors in your logs match to the ones in the TID. If so, try the resolution by running those novell-zenworks-configure commands.
Can you send the following information?
1) How many primary servers do you have in the zone?
2) If you have multiple servers, can the servers reach each other? Or are they connecting only to localhost in diagnostics page..
3) Can you send a screenshot of the diagnostics page ?
4) Can you send the zcc.log from the server where you see this failure?
5) Can you see whether you can ping using the IP addresses of the server..
6) On the servers, can you ensure whether the ports 61491, 61492, 61493, 61495 are listening and allowed in firewall.
Will request for more info if required.
Thanks for the reply
- We only have 1 server running Zenworks.
- See above.
- See attached.
- See attached, I have replaced the servers IP address on the request of my network manager.
- Pinging the server works fine.
- All those ports are open inbound, do they need to be open outbound as well? And I cannot see them in the list of listening ports in resource monitor.
If you require any further information please do not hesitate to ask.
From the logs, I suspect something wrong with the primary server's keystore file.. I would suggest to open an SR. We can take it from there.
Sadly we are a school and as part of our plan we do not get access to service requests. Whenever we have enquired about a service contract with our supplier they have said it would be about £2500 which is sadly more then we can afford, well that’s usually all we can get out of our supplier as they want us to use there engineers at £100 per hour instead, and I have struggled to find (or have time to try to find) someone else to help us with it.
Is there anything I can do to try to fix this?
Is there any kind of “pay as you go” SR service?
There should be "jmxagent" folder underneath the logdir. It should contain files such as
zen-jmxagent_61491.log (one for each of the listeners) which should give further insight.
Hi thanks for the reply
They all seem to be saying this over and over again, and i
[DEBUG][04/08/2020 14:47:058.914][ZEN JMX Agent][__z_160_49__][JMX Agent][starting connector server][ZENworks JMX Agent]
[DEBUG][04/08/2020 14:47:059.10][ZEN JMX Agent][__z_160_49__][JMX Agent][port is 61491][ZENworks JMX Agent]
[DEBUG][04/08/2020 14:47:059.133][ZEN JMX Agent][__z_160_49__][JMX Agent][keystore password is null..][ZENworks JMX Agent]
[DEBUG][04/08/2020 14:47:059.133][ZEN JMX Agent][__z_160_49__][JMX Agent][Trying to read password from passphrase file][ZENworks JMX Agent]
[DEBUG][04/08/2020 14:47:059.149][ZEN JMX Agent][__z_160_49__][JMX Agent][Use ssl is true][ZENworks JMX Agent]
[DEBUG][04/08/2020 14:47:059.149][ZEN JMX Agent][__z_160_49__][JMX Agent][Setting the ssl provider][ZENworks JMX Agent]
[DEBUG][04/08/2020 14:47:059.164][ZEN JMX Agent][__z_160_49__][JMX Agent][Original socket factory is null][ZENworks JMX Agent]
[DEBUG][04/08/2020 14:47:059.524][ZEN JMX Agent][__z_160_49__][JMX Agent][There is an exception ][java.lang.IllegalArgumentException: Unable to check if the cipher suites and protocols to enable are supported
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Caused by: java.net.SocketException: java.lang.NullPointerException
... 9 more
Caused by: java.lang.NullPointerException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
... 9 more
][ZENworks JMX Agent]
Do i need to set/enter a password somewhere?
Thanks for the help.
So something's going wrong in between
[DEBUG][04/09/2020 15:30:026.577][ZEN JMX Agent][zenworks][JMX Agent][Original socket factory is null][ZENworks JMX Agent]
[DEBUG][04/09/2020 15:30:027.43][ZEN JMX Agent][zenworks][JMX Agent][Current socket factory is com.novell.zenworks.javaagent.security.JmxSSLSocketFactory][ZENworks JMX Agent]
(from a working system)
Maybe what you get ...
DEBUG][04/08/2020 14:47:059.524][ZEN JMX Agent][__z_160_49__][JMX Agent][There is an exception ][java.lang.IllegalArgumentException: Unable to check if the cipher suites and protocols to enable are supported
really indicates a cipher mismatch of your OS and ZCM version / patchlevel. On a current 17.4.1 system the probe version e.g. is
Micro Focus ZENworks Probe Version 2.4.0-SNAPSHOT (r270824 2019-03-27 13:43 +0530)
So if you really are at 17.4.0 i'd think about patching up.
Unfortunately, as i have absolutely no clue of ZCM backend on Windows, i'll have to pass this one to the public.
Thanks for the help this has at least given me something to try, is there somewhere I can get/downlaod the correct probe version for my version? I have checked the server and it says 184.108.40.206
Thanks again for the help
Check PM. And use at your own risk. I'd doubt that it'll help too much unless the entire system gets lifted to 17.4.1.a.
I have now tried a different version of the probe and the same problem persists, i have uploaded the 17.4.1a update to my server so just wondering what is the best course of action now,
1: Should I update the server to 17.4.1a and hope this fixes the problem.
Would I have to make sure all the devices agents are updated before I move to 2020? As in the current situation that could be problematic in that the school is almost fully shut down (only children of key workers in) and all the devices are either off or not on site, so they would not receive the update until they come back on site which could be weeks or even months which would stop me from upgrading to 2020 for quite a long time.
2: Should I just upgrade to 2020 again hoping this fixes the problem. I know I will have the same problem with updating the device agents but this should happen when the machines come back on site and I won’t have multiple agent updates to do.
Thanks for the help.
I'd go for option #1for the time being. Less intrusive, especially facing the fact that you currently just want to resolve the "diagnostics / probe" issue. Just make sure to check all hints listed here