Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - normalcy

#1
General Support / Re: RPM build for Fedora 39?
December 12, 2023, 03:22:45 PM
Appreciate it thanks Filipp.  Fedora IoT has been an interesting platform for some appliances we've been testing with netxms and some containerized apps.
#2
General Support / RPM build for Fedora 39?
December 01, 2023, 06:05:39 AM
Hi, just wondering if you could build a RPM package set for Fedora 39? 

I know its fairly new, we use Fedora IoT atomic distro and it is a rolling release and has moved to fedora 39 now.  We're just waiting on the netxms agent packages to be available for 39 before we can upgrade from 38.

Kind regards.
#3
Hi Troffasky, are you using the legacy desktop client or the new desktop client?

I've noticed in the legacy client that in some screens right click doesn't seem to work unless you hold down the ctrl key as well.  Specifically I had that with the interfaces tab of a node, shift+select a range and hold down ctrl+right-click to get the popup.

Doesn't happen in the new client.
#4
Agreed, I would also like to see a selectable list of columns and/or drag and drop column re-ordering.

Main bugbear is that the interface status column is now usually off-screen now for all but the largest/widest of monitors.
#5
Feature Requests / Re: Client Reconnect
July 21, 2023, 07:17:43 AM
Also would like to see something here.  Example when upgrading the server and it disconnects the clients.  Would be great to have a tickbox option to 'try reconnect' and have a 5/10sec countdown a bit like the windows RDP client does when it gets disconnected.
#6
OK, if I delete and re-add those elements they now work.  Some internal identifiers changed?
#7
Hi, after upgrading to 4.1-377 I get an error on existing dashboards about missing DCI data.

It looks like the dashboard elements for rack diagram and DCI summary table are missing?  Editing properties of dashboard and trying to edit the dashboard elements for those types gives "Internal Error: no adaptor for dashboard element"
#8
General Support / Re: Overview Tab SLOW (4.1.283)
May 23, 2022, 04:58:18 AM
To add to this, the behaviour seems to only show up when you click on certain tabs in certain orders, eg:

  • Click on a node in the object explorer and then select a sub-tab for that node like interfaces or physical connections or performance.  When you come back to the overview sub-tab you will see everything collapsed.  Selecting another node and coming back to the current one refreshes the overview.
  • Alternatively, instead of selecting another node from object explorer and coming back, if you go to another parent tab like alarms or a dashboard tab and come back to the object details tab, the overview sub-tab won't be collapsed.  If you now select another sub-tab like interfaces or performance and come back to overview again its still not collapsed.
So given the second point above its possible depending on your habitual path through the MC you might not see this all the time.  But I was able to replicate it pretty consistently.  Going to and coming from parent tabs seem to force it to load in a way that doesn't collapse the overview headings.

This also happens on latest 4.1.333
#9
Hi all, upgraded recently to 4.1.283 server and nxmc. 

Just tried a walk with the MIB explorer and noticed that the "OID as text" column is not being populated for anything in the entire compiled MIB tree that netxms uses.

So the OID as text column at the bottom of the panel and the field on the right of the explorer are both only displaying ".iso" rather than the text path as in the past.

Tried recompiling with nxmibc and still the same.  Has anyone else noticed this?

edit:
to clarify, the MIB tree on the left has the OID as text built properly in the tree.  But that same tree path is not shown in the OID as text fields.  See attached screenshot.

The fact the tree works makes me think the compiler is building properly and perhaps its a bug in the nxmc?
#10
Hi, I tried updating using the package, and using the netxms-keyring.gpg however I found I still got the old version expiring on the 24/3 with those.

Seemed only the third option (curl --proto '=https' --tlsv1.2 -sSf https://packages.netxms.org/netxms.gpg | apt-key add -) gave me the updated key and allowed apt update to work?
#11
Hi after installing the windows x64 agent 4.0.2088 I can see in the windows event log errors under eventid 1000 regarding openssl and sqlite:


- Cannot load user agent notifications (local database is unavailable)
- Compile time OpenSSL version (101010bf) does not match runtime OpenSSL version (1010107f)
- Unable to load database driver module "sqlite.ddr": The specified module could not be found.
- Cannot load SQLite database driver
- Local database unavailable


I've noticed the agent seems to stop occasionally and some polls from the management console complains about missing policy database.  Is this related to the sqlite.ddr module missing on the agent side?


[09.02.2022 13:46:10] Checking node's capabilities...
[09.02.2022 13:46:10]    Checking NetXMS agent...
[09.02.2022 13:46:10]    NetXMS agent is active
[09.02.2022 13:46:10]    Reading list of available Windows Performance Counters...
[09.02.2022 13:46:11]    168 counters read
[09.02.2022 13:46:11]    File manager is not available
[09.02.2022 13:46:11]    Checking agent policy deployment
[09.02.2022 13:46:11]       Cannot get policy inventory from agent (Agent database failure)
#12
Announcements / Re: NetXMS 4.0 released
February 09, 2022, 05:13:22 AM
Thanks for the great work all.  I notice NPI files aren't published for the agent binaries, are they no longer needed to upload a package for deployment?
#13
Thanks Alex, I'm assuming I've got jetty on that VM from testing out the nxmc web console in the past.  Seems the 1.x series on my VM is not vulnerable to this CVE in any case.
#14
This github repo has hashes of vulnerable versions of the library and the link to the apache repo suggest ver 1.x might also be vulnerable too. 

I'm guessing installing jetty for the web console is what brings in log4j dependencies?
#15
General Support / Is netxms affected by CVE-2021-44228?
December 10, 2021, 11:45:05 PM
Hi, is netxms affected by log4j CVE-2021-44228?

Running a search on a debian VM with netxms installed shows:

# find / -name *log4j*
/var/lib/dpkg/info/liblog4j1.2-java.md5sums
/var/lib/dpkg/info/liblog4j1.2-java.list
/usr/share/java/slf4j-log4j12-1.7.22.jar
/usr/share/java/log4j-1.2-1.2.17.jar
/usr/share/java/log4j-over-slf4j.jar
/usr/share/java/ant-apache-log4j-1.9.9.jar
/usr/share/java/slf4j-log4j12.jar
/usr/share/java/log4j-1.2.jar
/usr/share/java/log4j-over-slf4j-1.7.22.jar
/usr/share/java/ant-apache-log4j.jar
/usr/share/maven-repo/org/apache/ant/ant-apache-log4j
/usr/share/maven-repo/org/apache/ant/ant-apache-log4j/debian/ant-apache-log4j-debian.pom
/usr/share/maven-repo/org/apache/ant/ant-apache-log4j/debian/ant-apache-log4j-debian.jar
/usr/share/maven-repo/org/apache/ant/ant-apache-log4j/1.9.9/ant-apache-log4j-1.9.9.jar
/usr/share/maven-repo/org/apache/ant/ant-apache-log4j/1.9.9/ant-apache-log4j-1.9.9.pom
/usr/share/maven-repo/org/slf4j/log4j-over-slf4j
/usr/share/maven-repo/org/slf4j/log4j-over-slf4j/1.7.22/log4j-over-slf4j-1.7.22.pom
/usr/share/maven-repo/org/slf4j/log4j-over-slf4j/1.7.22/log4j-over-slf4j-1.7.22.jar
/usr/share/maven-repo/org/slf4j/log4j-over-slf4j/debian/log4j-over-slf4j-debian.jar
/usr/share/maven-repo/org/slf4j/log4j-over-slf4j/debian/log4j-over-slf4j-debian.pom
/usr/share/maven-repo/org/slf4j/slf4j-log4j12
/usr/share/maven-repo/org/slf4j/slf4j-log4j12/1.7.22/slf4j-log4j12-1.7.22.jar
/usr/share/maven-repo/org/slf4j/slf4j-log4j12/1.7.22/slf4j-log4j12-1.7.22.pom
/usr/share/maven-repo/org/slf4j/slf4j-log4j12/debian/slf4j-log4j12-debian.jar
/usr/share/maven-repo/org/slf4j/slf4j-log4j12/debian/slf4j-log4j12-debian.pom
/usr/share/maven-repo/log4j
/usr/share/maven-repo/log4j/log4j
/usr/share/maven-repo/log4j/log4j/1.2.17/log4j-1.2.17.jar
/usr/share/maven-repo/log4j/log4j/1.2.17/log4j-1.2.17.pom
/usr/share/maven-repo/log4j/log4j/1.2.x/log4j-1.2.x.jar
/usr/share/maven-repo/log4j/log4j/1.2.x/log4j-1.2.x.pom
/usr/share/doc/liblog4j1.2-java
/usr/share/ant/lib/ant-apache-log4j.jar
/usr/share/jetty9/resources/log4j.properties


I've read online that some say log4j ver. 1.x is not vulnerable to the JNDI issue, but can't confirm that myself.  Is netxms affected do you think?  Or are these jars brought in with openjdk/jetty only and not used?