Custom Query (894 matches)

Here's a ticket to talk about the "growing memory use" problem. Using 0.8.0, I just ran the client on 62 nodes and saw this change in server memory usage:

Before:

root      2108  0.1  5.2 115444 108192 pts/11 S   Feb02   6:59 /usr/bin/python2.3 /usr/sbin/bcfg2-server

After:

root      2108  0.1  5.6 123176 115956 pts/11 S   Feb02   7:36 /usr/bin/python2.3 /usr/sbin/bcfg2-server

The only thing done between these data points is running the 62 clients. You'll also note that the beginning memory size is already quite a lot larger than the ~46MB we saw it using last week.

There seems to be a bug in the directory analysis. Here's two examples:

[[email protected]:/fc/gpfs-2.3.0-10]$ /usr/sbin/bcfg2 -q -n
...
Redhat[dryrun]: Entries to update:
...
Redhat[dryrun]: Directory: /disks/gpfs1
...

[[email protected]:/fc/gpfs-2.3.0-10]$ ls -ld /disks/
drwxr-xr-x  3 root root 4096 Dec  5 16:08 /disks/

[[email protected]:/fc/gpfs-2.3.0-10]$ ls -ld /disks/gpfs1/
drwxr-xr-x  2 root root 16384 Dec  5 16:10 /disks/gpfs1/

And here's one more:

[[email protected]:/var/db/bcfg]$ sudo /usr/sbin/bcfg2 -q -n
...
Redhat[dryrun]: Directory: /var/www/localhost/cgi-bin
Redhat[dryrun]: Directory: /var/www/localhost/htdocs
...

[[email protected]:/var/db/bcfg]$ ls -ld /var
drwxr-xr-x  22 root root 4096 Jan 16 15:01 /var/

[[email protected]:/var/db/bcfg]$ ls -ld /var/www
lrwxrwxrwx  1 root root 17 Jan 16 15:01 /var/www -> /disks/space0/www/

[[email protected]:/var/db/bcfg]$ ls -ld /disks/space0/www
drwxr-xr-x  15 root root 4096 Jan 19 08:07 /disks/space0/www/

[[email protected]:/var/db/bcfg]$ ls -ld /disks/space0/www/localhost
drwxr-xr-x  14 root root 4096 Jan 31 08:29 /disks/space0/www/localhost/

[[email protected]:/var/db/bcfg]$ ls -ld /disks/space0/www/localhost/htdocs
drwxrwxr-x  11 root admins 4096 Jan 25 22:59 /disks/space0/www/localhost/htdocs/

[[email protected]:/var/db/bcfg]$ ls -ld /disks/space0/www/localhost/cgi-bin
drwxr-xr-x  2 root root 4096 Jan 20 14:22 /disks/space0/www/localhost/cgi-bin/

The last one actually causes problems because it creates /var/www/localhost but removes the /var/www symlink to make it an actual directory which ain't good.

This confuses me since the Postinstall is acutally commented out, but I get this:

[[email protected]:/fc/qlafc-linux-8.01.01-1-install]$ /usr/sbin/bcfg2 -q -n Failure in Verify for entry: <Postinstall name="/sbin/new-kernel-pkg --package kernel --mkinitrd --depmod --install uname -r"/> File /usr/lib/python2.3/site-packages/Bcfg2/Client/Toolset.py, line 263, in VerifyEntry?

method = getattr(self, "Verify%s" % (entry.tag))

exceptions.AttributeError?: 'ToolsetImpl?' object has no attribute 'VerifyPostinstall?'

/usr/lib/python2.3/site-packages/Bcfg2/Client/Toolset.py:215: FutureWarning?: %u/%o/%x/%X of negative int will return a signed string in Python 2.4 and up

print "State verify evidently failed for %s" % (msg)

State verify evidently failed for <Element Postinstall at b7ca4488>

With this bundle: <Bundle name="qlogic-fc" version="2.0">

<System name="rh">

<!-- modprobe.conf needs some work for it to work right <ConfigFile? name="/etc/modprobe.conf"/> --> <Package name="qla2xxx"/> <Package name="scli"/> <!-- <Postinstall name="/sbin/new-kernel-pkg --package kernel --mkinitrd --depmod --install uname -r"/> -->

</System>

</Bundle>