RH Sat generated gigantic pulp logs in wrong location, trying to figure out why?

JockVSJock · 03-06-2017, 10:50 AM

Have a RHEL 6.8 hosting a RH Sat 6.10 and I have run out of space due to very large logs titled pulp_database. I'm not sure what is generating these because I can't read the logs:

Code:

[root@server mongodb]# file pulp_database.5 ; stat pulp_database.5
pulp_database.5: X11 SNF font data, LSB first
  File: `pulp_database.5'
  Size: 2146435072      Blocks: 4192312    IO Block: 4096   regular file
Device: fd09h/64777d    Inode: 650718      Links: 1
Access: (0600/-rw-------)  Uid: (  184/ mongodb)   Gid: (  490/ mongodb)
Access: 2017-03-06 10:45:40.481131848 -0600
Modify: 2017-03-06 05:49:17.841253311 -0600
Change: 2017-03-06 05:49:17.841253311 -0600
[root@server mongodb]#

I have a current subscription and GSS can't figure out why right now, so I'm turning to LQ to get further insight:

Code:

[root@server init.d]# ls -alS /var/lib/mongodb
total 6359776
-rw-------.  1 mongodb mongodb 2146435072 Mar  6 05:49 pulp_database.5
-rw-------.  1 mongodb mongodb 2146435072 Jan 19 09:31 pulp_database.6
-rw-------.  1 mongodb mongodb 1073741824 Jan 19 10:58 pulp_database.4
-rw-------.  1 mongodb mongodb  536870912 Jan 19 10:58 pulp_database.3
-rw-------.  1 mongodb mongodb  268435456 Jan 19 10:58 pulp_database.2
-rw-------.  1 mongodb mongodb  134217728 Jan 19 10:58 pulp_database.1
-rw-------.  1 mongodb mongodb   67108864 Feb 28 11:49 local.0
-rw-------.  1 mongodb mongodb   67108864 Mar  6 10:39 pulp_database.0
-rw-------.  1 mongodb mongodb   16777216 Feb 28 11:49 local.ns
-rw-------.  1 mongodb mongodb   16777216 Mar  6 05:49 pulp_database.ns
-rw-r--r--.  1 mongodb mongodb   14218103 Mar  1 03:19 mongodb.log.2017-03-01T09-23-01
-rw-r--r--.  1 mongodb mongodb   10335842 Jan 22 03:20 mongodb.log.2017-01-22T09-29-01
-rw-r--r--.  1 mongodb mongodb    3591385 Jan 29 03:31 mongodb.log.2017-01-29T09-33-03
-rw-r--r--.  1 mongodb mongodb    2751621 Jan  8 03:23 mongodb.log.2017-01-08T09-25-01
-rw-r--r--.  1 mongodb mongodb    2546596 Jan 15 03:30 mongodb.log.2017-01-15T09-32-01
-rw-r--r--.  1 mongodb mongodb    2414642 Mar  6 10:38 mongodb.log
-rw-r--r--.  1 mongodb mongodb    2053465 Jan  1 03:05 mongodb.log.2017-01-01T09-06-01
-rw-r--r--.  1 mongodb mongodb     418418 Dec 25 03:03 mongodb.log.2016-12-25T09-11-01
drwxr-xr-x.  3 mongodb mongodb       4096 Mar  1 03:23 .
drwxr-xr-x. 59 root    root          4096 Mar  6 03:45 ..
drwxr-xr-x.  2 mongodb mongodb       4096 Mar  4 22:47 journal
-rwxr-xr-x.  1 mongodb mongodb          5 Feb 28 11:49 mongod.lock
[root@server init.d]#

Red Hat's documentation is sparse for pulp. I can't find any man pages or apropose on the term pulp.

I found this:

http://docs.pulpproject.org/user-gui...roduction.html

Quote:

Platform Support Policy
CentOS/Red Hat Enterprise Linux (RHEL)

We currently support Red Hat Enterprise Linux 7 as well as CentOS 7.

Starting with Pulp 2.12, we no longer support Red Hat Enterprise Linux 6 or CentOS 6.

The Pulp team aims to provide RPM builds for the last two major releases of RHEL. For example, if the latest version is RHEL 8, builds should be available for RHEL 8 and RHEL 7. However, due to the long life cycle of these platforms and the relatively rapid development cycle of both Pulp and its dependencies, we may need to stop supporting the older platform before the next major release of RHEL. If this does occur, announcements will be made well in advance.

This wouldn't make sense as they claim to support RH Sat 6.10 on RHEL6 and RHEL7.

When looking at /etc/pulp/server.conf the logging isn't even turned on

Code:

# debugging_mode: false
# log_level: INFO

Shouldn't it be logging into /var/log not /var/lib/mongodb?

Anyways, I'm wondering what others think or if they have experienced this as well? And if so, how to fix.

thanks

dijetlo · 03-08-2017, 09:18 PM

Quote:

# debugging_mode: false
# log_level: INFO

Set INFO to warn or error.

Quote:

Pulp’s log level can be adjusted with the log_level setting in the [server] section of/etc/pulp/server.conf
This setting is optional and defaults to INFO. Valid choices are CRITICAL,
ERROR, WARNING, INFO, DEBUG, and NOTSET

I'd just set it to "NOTSET" since nobody seems to know how to read the logs. Since it defaults to "info" you may have to remove the "sheh" (octothorpe ) in front of the config line and change the setting.
That said, I know nothing at all about this piece of infrastructure and after a minimal review of the documentation I have to ask, what possible use is it?

JockVSJock · 03-09-2017, 05:52 AM

For some reason, the vanilla install of Puppet placed the logs under /var/lib/mongodb and I've switched them under /var/log/messages.

I will adjust that logging too as well to see if that can help in troubleshooting.

thanks