Highlighted
Absent Member.
Absent Member.
750 views

MongoDB Server Error


I was working on trying to installation my Sentinel location from the
default to a custom location. I backed up everything from the original
install and went through the process of uninstalling and reinstalling
7.3 for the time being. Once I have everything running and the Web UI
was working, I was set to restore the backup, however errors started
coming up during the restore that was something like this:

df: `/var/opt/novell/sentinel/3rdparty/mongodb/data': No such file or
directory
df: no file systems processed
/idm/opt/novell/sentinel/bin/si_db.sh: line 170: * 5 / 100 : syntax
error: operand expected (error token is "* 5 / 100 ")
Feb 26, 2016 9:04:22 AM com.mongodb.DBTCPConnector initDirectConnection
WARNING: Exception executing isMaster command on /127.0.0.1:27017
java.io.IOException: couldn't connect to [/127.0.0.1:27017]
bc:java.net.ConnectException: Connection refused
at com.mongodb.DBPort._open(DBPort.java:214)
at com.mongodb.DBPort.go(DBPort.java:107)
at com.mongodb.DBPort.go(DBPort.java:88)
at com.mongodb.DBPort.findOne(DBPort.java:143)
at com.mongodb.DBPort.runCommand(DBPort.java:148)
at
com.mongodb.DBTCPConnector.initDirectConnection(DBTCPConnector.java:548)
at
com.mongodb.DBTCPConnector.isMongosConnection(DBTCPConnector.java:372)
at com.mongodb.Mongo.isMongosConnection(Mongo.java:627)
at com.mongodb.DB.wrapCommand(DB.java:294)
at com.mongodb.DB.command(DB.java:272)
at com.mongodb.DB.command(DB.java:256)
at com.mongodb.DB.command(DB.java:313)
at com.mongodb.DB.command(DB.java:211)
at
com.mongodb.DB$AuthenticationCredentials.authenticate(DB.java:870)
at com.mongodb.DB.authenticateCommandHelper(DB.java:641)
at com.mongodb.DB.authenticate(DB.java:601)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.waitForDatabaseReady(MongoReconfig.java:401)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.getMongoClient(MongoReconfig.java:224)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.getMongoClient(MongoReconfig.java:214)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.reconfigReplicaSet(MongoReconfig.java:582)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.main(MongoReconfig.java:828)

Feb 26, 2016 9:04:22 AM com.mongodb.DBTCPConnector initDirectConnection
WARNING: Exception executing isMaster command on /127.0.0.1:27017
java.io.IOException: couldn't connect to [/127.0.0.1:27017]
bc:java.net.ConnectException: Connection refused
at com.mongodb.DBPort._open(DBPort.java:214)
at com.mongodb.DBPort.go(DBPort.java:107)
at com.mongodb.DBPort.go(DBPort.java:88)
at com.mongodb.DBPort.findOne(DBPort.java:143)
at com.mongodb.DBPort.runCommand(DBPort.java:148)
at
com.mongodb.DBTCPConnector.initDirectConnection(DBTCPConnector.java:548)
at
com.mongodb.DBTCPConnector.checkMaster(DBTCPConnector.java:527)
at
com.mongodb.DBTCPConnector.innerCall(DBTCPConnector.java:277)
at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:257)
at
com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:310)
at com.mongodb.DB.command(DB.java:274)
at com.mongodb.DB.command(DB.java:256)
at com.mongodb.DB.command(DB.java:313)
at com.mongodb.DB.command(DB.java:211)
at
com.mongodb.DB$AuthenticationCredentials.authenticate(DB.java:870)
at com.mongodb.DB.authenticateCommandHelper(DB.java:641)
at com.mongodb.DB.authenticate(DB.java:601)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.waitForDatabaseReady(MongoReconfig.java:401)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.getMongoClient(MongoReconfig.java:224)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.getMongoClient(MongoReconfig.java:214)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.reconfigReplicaSet(MongoReconfig.java:582)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.main(MongoReconfig.java:828)

Feb 26, 2016 9:04:22 AM com.mongodb.DBPortPool gotError
WARNING: emptying DBPortPool to /127.0.0.1:27017 b/c of error
java.io.IOException: couldn't connect to [/127.0.0.1:27017]
bc:java.net.ConnectException: Connection refused
at com.mongodb.DBPort._open(DBPort.java:214)
at com.mongodb.DBPort.go(DBPort.java:107)
at com.mongodb.DBPort.call(DBPort.java:74)
at
com.mongodb.DBTCPConnector.innerCall(DBTCPConnector.java:286)
at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:257)
at
com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:310)
at com.mongodb.DB.command(DB.java:274)
at com.mongodb.DB.command(DB.java:256)
at com.mongodb.DB.command(DB.java:313)
at com.mongodb.DB.command(DB.java:211)
at
com.mongodb.DB$AuthenticationCredentials.authenticate(DB.java:870)
at com.mongodb.DB.authenticateCommandHelper(DB.java:641)
at com.mongodb.DB.authenticate(DB.java:601)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.waitForDatabaseReady(MongoReconfig.java:401)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.getMongoClient(MongoReconfig.java:224)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.getMongoClient(MongoReconfig.java:214)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.reconfigReplicaSet(MongoReconfig.java:582)
at
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig.main(MongoReconfig.java:828)

Feb 26, 2016 9:04:22 AM
com.novell.sentinel.analytics.store.mongo.config.MongoReconfig
getMongoClient
SEVERE: com.mongodb.MongoException$Network: can't call something :
/127.0.0.1:27017/alerts

Now, during the restoration I allowed the system to restore itself even
with those errors. Once it was done, I setup to check if everything is
in place. Everything was working fine. Today, I was trying to stop and
start the server to chown the directories under novell instead of root.
Used the command service sentinel stop and start to have sentinel
running, when it was starting a similar error came up when starting
Sentinel. Again, I allowed Sentinel to go through its course and it was
working fine the WEB UI comes up and everything.

The original installation was going through default, but how our server
was setup was having one custom location with 1TB of space for saving
events. So, the original installation was a band-aid configuration where
the /var/opt/novell/sentinel folder was being moved to our custom
installation /idm and was laid out like this: /idm/novell/sentinel. We
used a symbolic link to allow the sentinel service to see the 1TB of
space. Understandably, Sentinel is not kind to symbolic links that in
this solution was working but it is difficult to handle how the sentinel
was behaving because of this configuration. Now, it is in a custom
location where all of the folder /opt - /etc - /var are in one location
and it much easier to handle.

What I want to know is does this error affect the installation it is
going now? How can I fix the error similar above? I want to know if the
backup is trying to find a location that does not exist anymore, or was
there errors during the backup phase that this came up? I was thinking
there could be a config file I can modify to fix the issue, but I may
not know where to look. By the looks of the error it seems to be a
script issue, or the backup is trying to find the original location.


--
dominique122
------------------------------------------------------------------------
dominique122's Profile: https://forums.netiq.com/member.php?userid=10786
View this thread: https://forums.netiq.com/showthread.php?t=55443

0 Likes
4 Replies
Highlighted
Absent Member.
Absent Member.

Re: MongoDB Server Error

dominique122,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit http://www.netiq.com/support and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request: https://www.netiq.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.netiq.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.netiq.com/faq.php

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your NetIQ Forums Team
http://forums.netiq.com


0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: MongoDB Server Error

It sounds like perhaps your ESEC_HOME and other variables are off. I have
done a bit of poking around on my default-locatino-install system, but
cannot find where that is set. Apparently I am going crazy.

The line that is failing should include the output of a 'df' command
against the directory used for baselining stuff, and that is not working,
perhaps because that variable is unset, probably because of df not working
in an attempt to get that space information. You can look at the script,
on the line mentioned in your error, to follow back the logic there.

I would definitely not use symlinks anywhere with Sentinel; try using a
"bind mount" instead. It is basically the same end result, only it is
done in a way that does not frustrate applications that are not handling
symlinks as you may like. Doing so from the command line is really easy,
and then you can make that mount permanent with a line in /etc/fstab so
hopefully that will improve things. For example:


#Make /idm/novell/sentinel... available from /var/opt/novell/sentinel
mount -o bind /idm/novell/sentinel/var/opt/novell/sentinel
/var/opt/novell/sentinel


Note that this does not automatically sub-mount subvolumes, so you may
want the -R option for mount to do that, but do not worry about that
unless you actually have sub-mounts somewhere under your
/idm/novell/sentinel/var/opt/novell/sentinel directory/mount already.

You would also need to do this for your other non-default locations, e.g.:


mount -o bind /idm/novell/sentinel/opt/novell/sentinel /opt/novell/sentinel
mount -o bind /idm/novell/sentinel/etc/opt/novell/sentinel
/etc/opt/novell/sentinel


Once done, see if things behave a little better.

In the future, I would probably not try moving the installation. It may
be a lot easier to build a new system, move over the configuration (ESM
has export/import as I recall), and then move over the archived data which
can be imported into the new system as well. If you can get your current
system working, then that's great too, but this was likely never
officially tested. Let us know your results and maybe that can be changed
in the future.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: MongoDB Server Error


I have only recently read your post, I will try this scenario to see if
it works better. I have recently been trying out different ways to
uninstall and reinstall, but wanted to ask does the event data stay on
the local partition even if you uninstall Sentinel? I have noticed that
events are are still there even in a clean install of Sentinel.


--
dominique122
------------------------------------------------------------------------
dominique122's Profile: https://forums.netiq.com/member.php?userid=10786
View this thread: https://forums.netiq.com/showthread.php?t=55443

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: MongoDB Server Error

I doubt all data ever linked to Sentinel are deleted, as that would be
really dangerous, so this is probably normal. The RPMs delete their
binaries, probably unmodified configuration files, etc., but unless
somebody tells the RPM's post-uninstall scripts, or a separate installer,
to go and clean up everything, something will persist by design.


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.