I think we can add lock option in 3.3. Regarding icon issues before refresh - looks like image library bug. What version you are using?
Best regards,
Victor
You can do full edit if you export dashboard into XML, edit it, and then import back. XML for individual elements can be edited directly from GUI (including layout properties).
Best regards,
Victor
Hi,
we decided to drop combined server/console package as part of overall effort to reduce number of packages and thus required support efforts. Actually we did expect that in most cases server is installed on separate machine and users are connected from remote workstations.
Best regards,
Victor
SSH connections are performed from netxms agent. It is either a proxy, or agent on netxms server. These agents need to have ssh subagent loaded (SubAgent=ssh.nsm in config file).
NetXMS takes CPU load information from /proc/stat. We just read this file once per second, calculate deltas and divide the deltas by sum of them.
Please run below command on a container that got into that state and share the output:
n=1; while [ $n -le 60 ]; do cat /proc/stat | grep cpu0; sleep 1; n=$((n+1)); done
Then restart the container and get these stats again so we could have some data for comparison.
dhcp or
some nefarious person has interjected a device in the line or
a windows machine has reset a programable network device, etc.
but most likely dhcp devices. Netxms follows the ip not the mac.
Hello Victor,
as you recomendation, I did what you said (download the new version) and everything goes ok, maybe was about broken package. Thank you for your fast reply.
Thanks and have a nice day!
Sorry, I'm really a newbie (I think you can tell), I'm taking over someone's job...
The "Snmp Location KO" card just didn't exist.
After create it, it's ok.
Many thanks.
Best regards,
BB
Hello Victor,
thanks for Your fast response!
While preparing the download of the images for You I realized that there was a problem in display the copy of my file from my new server on windows too. I have seen, that there was a difference in bytecount between the original file on my old netxmsserver and that on my new server.
I did the transfer via filezilla initiated from the new server one more time and got the same results (concerning bytecount differences). Filezilla was configured for automatic detection of transfertype (configured as standard). When configuring filezilla explecitly for binary transfertype the file is transfered correctly and has the original size.
This is a behavour I have never seen before with filezilla.
The images transfered in binary type via filezilla all work fine with the new implementation of Your image library tool now. For administration the responsetimes of the tool are really great now even for large images.
Sorry for posting the problem that was generated via an other tool!
Best regards
Georg