Custom Query (894 matches)
Results (10 - 12 of 894)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #748 | desai | tcampbel | fixed | detect hanging gamin/fam server |
| Description |
16:43:13 < HCoyote> desai: so, at some point we encountered this in the past and the symptom threw an error that looked like "Hit event timeout without getting any
events; GAMIN/FAM problem?"
16:43:26 < desai> yeah, we can detect it upon startup pretty easily
16:43:27 < HCoyote> in this case, i can't find an error that would indicate a gamin problem.
16:43:28 < desai> oooh
16:43:35 < desai> we could add a watchdog
16:43:44 < desai> that would be pretty easy, and would catch cases like this
16:43:49 < HCoyote> is there some sort of feedback loop then?
16:44:03 < desai> just keep a timestamp in the gamin driver for the last event seen
add a method to have bcfg2-server detect if gam_server has hung and let admin know that it needs to be restarted. |
|||
| #765 | desai | tcampbel | fixed | YUMng __init__ fails to properly set up repo when base system is RHEL5 updating from Satellite |
| Description |
RHEL5 systems use yum to get their updates. When a RHEL5 system is configured to use Satellite instead of a classic yum repository, yum runs a plugin to translate Satellite into yumspeak. Unfortunately, it appears that the default yum/init__.py:doGenericSetup specifically disables the instantiation of plugins. Because YUMng.py:init calls doGenericSetup as part of the init of the yum repo for querying if it finds that the system supports the doGenericSetup attribute, yum basically self-configures with the Satellite plugin disabled. I'm not sure what the correct work around is at this point. Commenting out the doGenericSetup call does the "right" thing but I don't know if it's the correct thing. I test this with doGenericSetup in a default uncommented state by twiddling the self._getConfig(init_plugins=False) in yum/init.py to be true and version checking began working. |
|||
| #931 | jjneely | tac_ <[email protected]…> | fixed | YUMng fails installing a custom GPG key |
| Description |
System: Centos 5 Version: trunk r6046 base-packages.xml: <Bundle name='base-packages'>
</Bundle> client debug: Verifying package instances for gpg-pubkey Verifying: gpg-pubkey-e8562897-459f07a4 Verifying: gpg-pubkey-bcbecbd4-4c2df0e1
... Installing ConfigFile? /etc/pki/rpm-gpg/RPM-GPG-KEY-myownkey Running YUMng.Install() Installing GPG keys. Installed gpg-pubkey-bcbecbd4-4c2df0e1 YUMng.Install() call failed: Traceback (most recent call last):
AttributeError?: YUMng instance has no attribute 'getinstalledgpg' The Following Bundles have been modified:
... Verifying package instances for gpg-pubkey Verifying: gpg-pubkey-e8562897-459f07a4 Verifying: gpg-pubkey-bcbecbd4-4c2df0e1
|
|||
