Absurd rate of events logging to /var/db/mongodb/mongod.log.

[Isabella Borgward]

/var/db/mongodb/mongod.log is full of this:

Code: [Select]

2024-07-05T11:08:19.312+0000 I NETWORK  [conn742973] end connection 127.0.0.1:9158 (6 connections now open)
2024-07-05T11:08:20.414+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:9165 #742975 (7 connections now open)
2024-07-05T11:08:20.414+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:9166 #742976 (8 connections now open)
2024-07-05T11:08:20.414+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:9167 #742977 (9 connections now open)
2024-07-05T11:08:20.414+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:9168 #742978 (10 connections now open)
2024-07-05T11:08:20.415+0000 I NETWORK  [conn742975] received client metadata from 127.0.0.1:9165 conn742975: { driver: { name: "mongo-go-driver", version: "v1.7.0" }, os: { type: "freebsd", architecture: "amd64" }, platform: "go1.19.3" }
2024-07-05T11:08:20.415+0000 I NETWORK  [conn742976] received client metadata from 127.0.0.1:9166 conn742976: { driver: { name: "mongo-go-driver", version: "v1.7.0" }, os: { type: "freebsd", architecture: "amd64" }, platform: "go1.19.3" }
2024-07-05T11:08:20.415+0000 I NETWORK  [conn742977] received client metadata from 127.0.0.1:9167 conn742977: { driver: { name: "mongo-go-driver", version: "v1.7.0" }, os: { type: "freebsd", architecture: "amd64" }, platform: "go1.19.3" }
2024-07-05T11:08:20.415+0000 I NETWORK  [conn742978] received client metadata from 127.0.0.1:9168 conn742978: { driver: { name: "mongo-go-driver", version: "v1.7.0" }, os: { type: "freebsd", architecture: "amd64" }, platform: "go1.19.3" }
2024-07-05T11:08:20.716+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:9171 #742979 (11 connections now open)
2024-07-05T11:08:20.716+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:9172 #742980 (12 connections now open)
2024-07-05T11:08:20.716+0000 I NETWORK  [conn742979] received client metadata from 127.0.0.1:9171 conn742979: { driver: { name: "mongo-go-driver", version: "v1.7.0" }, os: { type: "freebsd", architecture: "amd64" }, platform: "go1.19.3" }
2024-07-05T11:08:20.716+0000 I NETWORK  [conn742980] received client metadata from 127.0.0.1:9172 conn742980: { driver: { name: "mongo-go-driver", version: "v1.7.0" }, os: { type: "freebsd", architecture: "amd64" }, platform: "go1.19.3" }
2024-07-05T11:08:20.720+0000 I NETWORK  [conn742980] end connection 127.0.0.1:9172 (11 connections now open)
2024-07-05T11:08:20.720+0000 I NETWORK  [conn742978] end connection 127.0.0.1:9168 (10 connections now open)
2024-07-05T11:08:20.720+0000 I NETWORK  [conn742975] end connection 127.0.0.1:9165 (9 connections now open)
2024-07-05T11:08:20.721+0000 I NETWORK  [conn742976] end connection 127.0.0.1:9166 (8 connections now open)
2024-07-05T11:08:20.721+0000 I NETWORK  [conn742977] end connection 127.0.0.1:9167 (7 connections now open)
2024-07-05T11:08:20.721+0000 I NETWORK  [conn742979] end connection 127.0.0.1:9171 (6 connections now open)
2024-07-05T11:08:21.831+0000 I NETWORK  [listener] connection accepted from 127.0.0.1:9177 #742981 (7 connections now open)


You can see that there were 18 events in 1 second here. I have tried restarting mongodb but it didn't make any difference. Additionally, the log file does not get rotated. I can see that it was rotated once but then never again.

Code: [Select]

root@router:/var/db/mongodb # ls -alh mongod.log*
-rw-------  1 mongodb  mongodb   336M Jul  5 11:08 mongod.log
-rw-------  1 mongodb  mongodb   4.8K May 10 11:15 mongod.log.2024-05-10T11-15-15



[sy]

Hi,

Thanks for reporting the issue. Zenarmor injects ipdr files continuously to the DB. So it creates events on the MongoDB site. For the log rotate issue, We have reproduced it and it will be fixed with the upcoming release.

[Isabella Borgward]

As I care way more about disk usage and storage I/O than I do about these events, I have put
quiet: true
in the logging section in mongod.conf. This has reduced it to a mere 5-10 events per second