Hi Alberto,

yes, I take a look in the /var/log/mongodb/mongod.log and there occured no 
significant problems, I think:

----- /var/log/mongodb/mongod.log -----

2015-11-12T11:28:11.335+0100 [initandlisten] MongoDB starting : pid=27682 
port=27017 dbpath=/var/lib/mongodb 64-bit host=server11.idmz.tachtler.net
2015-11-12T11:28:11.335+0100 [initandlisten] db version v2.6.11
2015-11-12T11:28:11.335+0100 [initandlisten] git version: nogitversion
2015-11-12T11:28:11.335+0100 [initandlisten] OpenSSL version: OpenSSL 
1.0.1e-fips 11 Feb 2013
2015-11-12T11:28:11.336+0100 [initandlisten] build info: Linux 
buildvm-08.phx2.fedoraproject.org 4.1.4-100.fc21.x86_64 #1 SMP Tue Aug 4 
03:25:05 UTC 2015 x86_64 BOOST_LIB_VERSION=1_53
2015-11-12T11:28:11.336+0100 [initandlisten] allocator: tcmalloc
2015-11-12T11:28:11.336+0100 [initandlisten] options: { command: [ "run" ], 
config: "/etc/mongod.conf", net: { bindIp: "127.0.0.1", unixDomainSocket: { 
pathPrefix: "/var/run/mongodb" } }, processManagement: { fork: true, 
pidFilePath: "/var/run/mongodb/mongod.pid" }, security: { authorization: 
"enabled" }, storage: { dbPath: "/var/lib/mongodb", smallFiles: true }, 
systemLog: { destination: "file", path: "/var/log/mongodb/mongod.log", 
quiet: true } }
2015-11-12T11:28:11.336+0100 [initandlisten] 
2015-11-12T11:28:11.336+0100 [initandlisten] ** WARNING: Readahead for 
/var/lib/mongodb is set to 4096KB
2015-11-12T11:28:11.336+0100 [initandlisten] **          We suggest setting 
it to 256KB (512 sectors) or less
2015-11-12T11:28:11.336+0100 [initandlisten] **          
http://dochub.mongodb.org/core/readahead
2015-11-12T11:28:11.357+0100 [initandlisten] journal 
dir=/var/lib/mongodb/journal
2015-11-12T11:28:11.357+0100 [initandlisten] recover : no journal files 
present, no recovery needed
2015-11-12T11:28:14.892+0100 [initandlisten] preallocateIsFaster=true 3.52
2015-11-12T11:28:17.852+0100 [initandlisten] preallocateIsFaster check took 
6.493 secs
2015-11-12T11:28:17.908+0100 [initandlisten] waiting for connections on 
port 27017
2015-11-12T11:28:18.258+0100 [conn3]  authenticate db: graylog { 
authenticate: 1, user: "grayloguser", nonce: "xxx", key: "xxx" }
2015-11-12T11:36:01.716+0100 [conn3] command graylog.$cmd command: delete { 
delete: "cluster_events", ordered: true, writeConcern: { w: 1, fsync: true 
}, deletes: [ { q: { timestamp: { $lt: 1447320961561 } }, limit: 0 } ] } 
keyUpdates:0 numYields:0  reslen:40 154ms

----- /var/log/mongodb/mongod.log -----

*BUT*, sometimes I can see following messages:

*2015-11-10T14:01:02.889+0100 [conn4] Unauthorized not authorized on admin 
to execute command { serverStatus: true }*

Thank you,
Klaus.

Am Dienstag, 10. November 2015 17:41:24 UTC+1 schrieb Alberto Frosi:
>
> Hi all,
> can you take a look in mongo.log to check message error?
> Alberto
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/77108b57-2a59-408a-8f9b-232b7401c150%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to