Archive for the ‘ Problems-Errors-Bugs ’ Category

OpenLDAP crash under barracuda query

The problem appear just after I installed a barracuda V400 and configured the LDAP verification for a valid recipients.

On the server the process just died. At the end of the log I was able to see things like this:

Jul 25 06:30:24 XXXXXXXXX slapd[8327]: daemon: read active on 94
Jul 25 06:30:24 XXXXXXXXX slapd[8327]: daemon: epoll: listen=7 busy
Jul 25 06:30:24 XXXXXXXXX  slapd[8327]: daemon: epoll: listen=8 busy
Jul 25 06:30:24 XXXXXXXXX  slapd[8327]: daemon: epoll: listen=9 busy
Jul 25 06:30:24 XXXXXXXXX  slapd[8327]: daemon: epoll: listen=10 active_threads=0 tvp=NULL
Jul 25 06:30:24 XXXXXXXXX  slapd[8327]: daemon: epoll: listen=11 active_threads=0 tvp=NULL
Jul 25 06:30:29 XXXXXXXXX  slapd[8327]: daemon: activity on 1 descriptor
Jul 25 06:30:29 XXXXXXXXX  slapd[8327]: daemon: activity on:
Jul 25 06:30:29 XXXXXXXXX  slapd[8327]:

I opened a case at barracuda support and after few check with their engineer they told me this was a known issue with the Exchange Antivirus.

So the solution they provided me was to disable the exchange antivirus, in our case this was not a problem, we just don’t have exchange.. I probably just havn’t seen this option during my initial setup..

 

So to disable this option go to ADVANCED => Exchange Antivirus:

Check the “No” radio button for “Enable Exchange Antivirus” to disable it. At this time our LDAP haven’t crashed since this change..

Spacewalk 2.1 Problem pushing config files to systems. ( ‘str’ object has no attribute ‘value’ )

I have a problem publishing config file to my registered system using satellite 2.1

When I run rhn_check on the systems I always get a: D: Sending back response(49, “Failed deployment, rolled back:  ‘str’ object has no attribute ‘value'”, {})

I found a bug opened few days ago, so I’m curently working with a DEV on this, it look like a bug, if you too face this bug, please comment on the bugreport!

https://bugzilla.redhat.com/show_bug.cgi?id=1087786

Here’s the full output of rhn_check -vv:

D: opening db environment /var/lib/rpm cdb:mpool:joinenv
D: opening db index /var/lib/rpm/Packages rdonly mode=0x0
D: locked db index /var/lib/rpm/Packages
D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/*.key
D: couldn't find any keys in /var/lib/rpm/pubkeys/*.key
D: loading keyring from rpmdb
D: opening db index /var/lib/rpm/Name rdonly mode=0x0
D: added key gpg-pubkey-0608b895-4bd22942 to keyring
D: added key gpg-pubkey-863a853d-4f55f54d to keyring
D: added key gpg-pubkey-b3892132-4c63febc to keyring
D: added key gpg-pubkey-c105b9de-4e0fd3a3 to keyring
D: Using legacy gpg-pubkey(s) from rpmdb
D: opening db index /var/lib/rpm/Providename rdonly mode=0x0
D: check_action{'action': "<?xml version='1.0'?>\n<methodCall>\n<methodName>configfiles.deploy</methodName>\n<params>\n<param>\n<value><struct>\n<member>\n<name>files</name>\n<value><array><data>\n<value><struct>\n<member>\n<name>config_channel</name>\n<value><string>base-sepaq</string></value>\n</member>\n<member>\n<name>username</name>\n<value><string>root</string></value>\n</member>\n<member>\n<name>encoding</name>\n<value><string>base64</string></value>\n</member>\n<member>\n<name>checksum</name>\n<value><string>ec3c5c05a212c20ca690def7c2d3c79d</string></value>\n</member>\n<member>\n<name>filetype</name>\n<value><string>file</string></value>\n</member>\n<member>\n<name>delim_start</name>\n<value><string>{|</string></value>\n</member>\n<member>\n<name>delim_end</name>\n<value><string>|}</string></value>\n</member>\n<member>\n<name>symlink</name>\n<value><string></string></value>\n</member>\n<member>\n<name>modified</name>\n<value><string></string></value>\n</member>\n<member>\n<name>groupname</name>\n<value><string>root</string></value>\n</member>\n<member>\n<name>file_contents</name>\n<value><string>I3hmZ3hneGdmCiNBQUFBQUFBQUFBQUFBQUFBQUEKI0JCQkJCQkJCQkJCQkJCQkJCQkJCQgojQ0ND\nQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDCiNEREREREREREREREREREREREREREREREREREQK\n</string></value>\n</member>\n<member>\n<name>filemode</name>\n<value><int>644</int></value>\n</member>\n<member>\n<name>checksum_type</name>\n<value><string>md5</string></value>\n</member>\n<member>\n<name>path</name>\n<value><string>/etc/aaa</string></value>\n</member>\n<member>\n<name>selinux_ctx</name>\n<value><string>etc_t</string></value>\n</member>\n<member>\n<name>revision</name>\n<value><int>4</int></value>\n</member>\n</struct></value>\n</data></array></value>\n</member>\n</struct></value>\n</param>\n</params>\n</methodCall>\n", 'version': 2, 'id': 126}
updateLoginInfo() login info
D: login(forceUpdate=True) invoked
logging into up2date server
D: rpcServer: Calling XMLRPC up2date.login
D: writeCachedLogin() invoked
D: Wrote pickled loginInfo at 1398439576.61 with expiration of 1398443176.61 seconds.
successfully retrieved authentication token from up2date server
D: logininfo:{'X-RHN-Server-Id': 1000010006, 'X-RHN-Auth-Server-Time': '1398439576.41', 'X-RHN-Auth': 'M0X4upKQItLGbt4W6CMUjQ==', 'X-RHN-Auth-Channels': [['prod-centos6-x86_64', '20140324072756', '1', '1'], ['prod-epel_rhel6_x86_64', '20140413154109', '0', '1'], ['prod-spacewalk-client-2.1-centos6-x86_64', '20140414235043', '0', '1'], ['prod-rhel6-vm-x64-esx5-5', '20140416225329', '0', '1']], 'X-RHN-Auth-User-Id': '', 'X-RHN-Auth-Expire-Offset': '3600.0'}
D: handle_action{'action': "<?xml version='1.0'?>\n<methodCall>\n<methodName>configfiles.deploy</methodName>\n<params>\n<param>\n<value><struct>\n<member>\n<name>files</name>\n<value><array><data>\n<value><struct>\n<member>\n<name>config_channel</name>\n<value><string>base-sepaq</string></value>\n</member>\n<member>\n<name>username</name>\n<value><string>root</string></value>\n</member>\n<member>\n<name>encoding</name>\n<value><string>base64</string></value>\n</member>\n<member>\n<name>checksum</name>\n<value><string>ec3c5c05a212c20ca690def7c2d3c79d</string></value>\n</member>\n<member>\n<name>filetype</name>\n<value><string>file</string></value>\n</member>\n<member>\n<name>delim_start</name>\n<value><string>{|</string></value>\n</member>\n<member>\n<name>delim_end</name>\n<value><string>|}</string></value>\n</member>\n<member>\n<name>symlink</name>\n<value><string></string></value>\n</member>\n<member>\n<name>modified</name>\n<value><string></string></value>\n</member>\n<member>\n<name>groupname</name>\n<value><string>root</string></value>\n</member>\n<member>\n<name>file_contents</name>\n<value><string>I3hmZ3hneGdmCiNBQUFBQUFBQUFBQUFBQUFBQUEKI0JCQkJCQkJCQkJCQkJCQkJCQkJCQgojQ0ND\nQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDCiNEREREREREREREREREREREREREREREREREREQK\n</string></value>\n</member>\n<member>\n<name>filemode</name>\n<value><int>644</int></value>\n</member>\n<member>\n<name>checksum_type</name>\n<value><string>md5</string></value>\n</member>\n<member>\n<name>path</name>\n<value><string>/etc/aaa</string></value>\n</member>\n<member>\n<name>selinux_ctx</name>\n<value><string>etc_t</string></value>\n</member>\n<member>\n<name>revision</name>\n<value><int>4</int></value>\n</member>\n</struct></value>\n</data></array></value>\n</member>\n</struct></value>\n</param>\n</params>\n</methodCall>\n", 'version': 2, 'id': 126}
D: handle_action actionid = 126, version = 2
D: do_call configfiles.deploy({'files': [{'config_channel': 'base-seq', 'username': 'root', 'encoding': 'base64', 'checksum': 'ec3c5c05a212c20ca690def7c2d3c79d', 'filetype': 'file', 'delim_start': '{|', 'modified': '', 'symlink': '', 'groupname': 'root', 'delim_end': '|}', 'selinux_ctx': 'etc_t', 'filemode': 644, 'file_contents': 'I3hmZ3hneGdmCiNBQUFBQUFBQUFBQUFBQUFBQUEKI0JCQkJCQkJCQkJCQkJCQkJCQkJCQgojQ0ND\nQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDCiNEREREREREREREREREREREREREREREREREREQK\n', 'checksum_type': 'md5', 'path': '/etc/aaa', 'revision': 4}]},){'cache_only': None}
'str' object has no attribute 'value'
D: Sending back response(49, "Failed deployment, rolled back: 'str' object has no attribute 'value'", {})
D: do_call packages.checkNeedUpdate('rhnsd=1',){}
D: opening db environment /var/lib/rpm cdb:mpool:joinenv
D: opening db index /var/lib/rpm/Packages rdonly mode=0x0
D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/*.key
D: couldn't find any keys in /var/lib/rpm/pubkeys/*.key
D: loading keyring from rpmdb
D: opening db index /var/lib/rpm/Name rdonly mode=0x0
D: added key gpg-pubkey-0608b895-4bd22942 to keyring
D: added key gpg-pubkey-863a853d-4f55f54d to keyring
D: added key gpg-pubkey-b3892132-4c63febc to keyring
D: added key gpg-pubkey-c105b9de-4e0fd3a3 to keyring
D: Using legacy gpg-pubkey(s) from rpmdb
D: opening db index /var/lib/rpm/Providename rdonly mode=0x0
D: closed db index /var/lib/rpm/Providename
D: closed db index /var/lib/rpm/Name
D: closed db index /var/lib/rpm/Packages
D: closed db environment /var/lib/rpm
Loaded plugins: fastestmirror, rhnplugin
Config time: 0.033
D: rpcServer: Calling XMLRPC up2date.listChannels
This system is receiving updates from RHN Classic or Red Hat Satellite.
Setting up Package Sacks
Loading mirror speeds from cached hostfile
 * base: centos.mirror.rafal.ca
 * extras: centos.mirror.rafal.ca
 * updates: centos.mirror.rafal.ca
pkgsack time: 0.233
rpmdb time: 0.000
Checking for new repos for mirrors
repo time: 0.001
D: local action status: (0, 'rpm database not modified since last update (or package list recently updated)', {})
D: rpcServer: Calling XMLRPC registration.welcome_message
D: closed db index /var/lib/rpm/Providename
D: closed db index /var/lib/rpm/Name
D: closed db index /var/lib/rpm/Packages
D: closed db environment /var/lib/rpm

Fedora 15 problem with Empathy and you are unable to connect to msn ?

LAST UPDATE #2: An update as been pushed in the Fedora Testing repo and correct this problem. If you want to install this update you just have to use the enablerepo feature just like that:

#yum install papyon --enablerepo=updates-testing

The repository is enabled only for this update!


UPDATE #1: This has worked for me yesterday, but it’s not working anymore.. I haven’t been able to fix the issue… Please report your test and problems in the bug report at: https://bugzilla.redhat.com/show_bug.cgi?id=750884



Papyon : Can't login in Windows live : accountab.py:202:_HandleABFindAllResponse:AttributeError: 'NoneType' object has no attribute 'find'

If you get this erorr reported by ABRT on Fedora 15 and you are unable to connect to msn with empathy, here’s a workaround.

Here’s the bug report if you want to share your problem regarding this issue:

https://bugzilla.redhat.com/show_bug.cgi?id=750884

The workaround consist of a upstram patch that has been released. It will probably work it’s way to fedora soon but for now you need to do some work by hand.

Here you can get the code to update: http://cgit.collabora.com/git/user/maiku/papyon.git/commit/?h=bug-42689&id=011201e47004538e732f247bfeb21634c6e1d97f

As you can see you have to edit three files. The path I will give you is the exact path under Fedora 15 but can change with other distrib. The line with “-” need to be commented with a “#” at the beginning of the line, and the line with a + need to be added..

1 – /usr/lib/python2.7/site-packages/papyon/service/description/SingleSignOn/RequestMultipleSecurityTokens.py

- CONTACTS = ("contacts.msn.com", "MBI")
+ CONTACTS = ("local-bay.contacts.msn.com", "MBI")
2 – /usr/lib/python2.7/site-packages/papyon/service/description/AB/__init__.py
-url = "http://contacts.msn.com/abservice/abservice.asmx"
+url = "http://local-bay.contacts.msn.com/abservice/abservice.asmx"
3 – /usr/lib/python2.7/site-packages/papyon/service/description/Sharing/__init__.py
-url = "http://contacts.msn.com/abservice/SharingService.asmx"
+url = "http://local-bay.contacts.msn.com/abservice/SharingService.asmx"

That’s it!

MythTV and MythWEB on Fedora 14

I finally get everything working correctly… I don’t have a lot of time for this post, but I want to share how I corrected few problems I had.

1 – Sound problem. This one is cause by MythTV having problem dealing with PulseAudio. The solution was simple, and it was to set the MythTV FrontEnd audio device to ALSA:pulse … There’s no auto discovery for this.

The second problem was with MythWeb. I was unable to load the web interface.

Here’s the errors I got:

Apache logs:
PHP Fatal error:  Failed to open translation file:  modules_path/_shared/lang/English.lang in /usr/share/mythweb/classes/Translate.php on line 172
MythTV Backend:
MainServer, Warning: Unknown socket closing MythSocket

So I don’t think this is the best fix ever. But if you’re like me and totally pissed off do this:

# vim /usr/share/mythweb/classes/Translate.php

Modify this section (original) :

    // Load the primary language file, or English if the other doesn't exist.
        if (file_exists(modules_path.'/_shared/lang/'.$language.'.lang'))
            $path = modules_path.'/_shared/lang/'.$language.'.lang';
        else
            $path = modules_path.'/_shared/lang/English.lang';

After modification it should look like this:

       //if (file_exists(modules_path.'/_shared/lang/'.$language.'.lang'))
        if (file_exists('/usr/share/mythweb/modules/_shared/lang/English.lang'))
            $path = '/usr/share/mythweb/modules/_shared/lang/English.lang';
        else
            $path = '/usr/share/mythweb/modules/_shared/lang/English.lang';

And voila… everything is working now. Feel free to ask question I know there’s not a lot of detail in this post but I’ve run into a lot of problem with this setup, so I can probably help!

++

Howto fix IRobot Roomba left or right wheel

My Roomba 530 started to spin around his right wheel few week ago. It happened few times and then more often and after that it was doing only this… So I tried all the iRobot suggested “repair” method, but there’s not a lot to do on iRobot  website regarding problem with your right or left wheel. So I was faced with the reality, I will have to buy a new right wheel module. It’s not that expensive you can find it on ebay for around 20$ shipped but I’m the kind of guy who don’t like to buy replacement part when I can fix it!

After few test and diagnostic, I confirmed that the problem was the right wheel. It was unable to spin, but if I just pushed a little bit the roomba, it start working. So I put the roomba on it’s back and tried to move both wheels and found out that the resistance on both wheel wasn’t the same and after a closer look I was pretty sure there was hairs stuck in the wheel module. Then I opened the roomba and I took few pics of my adventure in case that my idea will work, it can always help someone else! If your problem look like mine, you can follow those steps, maybe you will be able to fix it! If anyone found a way to open the wheel contained in the wheel module let us know I was unable to find anything on the net regarding this..

This is a “Try at your own risk” repair. This had fixed my wheel but I don’t know yet if it will last for weeks or months.. do this only if you’re desperate and you tried all other option suggested by iRobot support.

Ok so here’s the first step I tried before doing the main repair, you should probably try every step before, in case your problem is not the same as mine!

Try the iRobot suggested fix method

If you roomba say “Please Inspect and Clean Roomba’s left (or right) Wheel” or if, like me, your roomba spin around a wheel and if you push it a little bit it started to go straight and then restart to spin.

Try those url from iRobot support website :

http://homesupport.irobot.com/app/answers/detail/a_id/498

http://homesupport.irobot.com/app/answers/detail/a_id/805

Fixing hair stuck in the wheel module

If those steps fail for you, and you contacted iRobot support and they told you you’ll need a new wheel module or you feel a different resistance when you spin the wheel, maybe you’re like me and there’s hair or anything stuck in the wheel module. You can try those steps, again, at your own risk.

The idea I had was to used a hair removal mousse, to “soften” the hair stuck in the wheel mechanism. Here’s how to open your roomba 500 and insert the veet foam into the wheel and add oil for lubrication after that.

  • Put your roomba on it’s back. You can put a towel or something smooth under it if you don’t want to scratch the top. Unscrew the side brush and remove it with a flat screwdriver. On the main plate you can see 4 screw with arrow pointing, unscrew them.

  • Remove the plate, and you’ll see the battery. Pull out the battery carefully.

  • Now you should have removed battery and you should be able to locate both side wheels.

  • Remove those three screw.

 

  • Pull out the wheel module gently. Now you should have the wheel module in your hand. I took a picture to show you how to “open” the module but I didn’t remove it on this picture. you can do it like this but it’s hard to keep everything clean…
  • As you can see on the picture, take a thin knife and you have to insert the knife horizontally in the small crack between the inner plastic piece and the rubber wheel. You’ll feel the plastic moving.. be careful to don’t cut or damage the wheel or the plastic.. When your knife is between both parts, lift the knife as it is on the picture so you’ll see a small crack. this is where you’ll need to spray the hair removal mousse… I didn’t show it on the picture because it was already done, and I don’t want do this again.. it’s not easy as it could seem, you may need another hand to keep everything in place and put the hair removal foam… Put a decent amount of foam, you want it to reach the center of the wheel where the air are stuck.

  • After you put the foam into the wheel let it “work” for almost 10 minutes.
  • Roll the wheel and see if you still feel a resistance if you don’t it look good!
  • I wiped the extra foam and I added oil or something to lubricate the center of the wheel. Be careful don’t put too much oil or lubricant because hair and dust will stick to this!

That’s it, put everything back in place. and try your roomba. Mine took almost 5 minutes of “under supervision” first run. After that the wheel was fine!

Let me know if this helped you or if you have another trick to fix the wheels! This is certainly not the best way to do it, but maybe my wheel will survive 1-2 months more!

@+

Fedora 13 liveusb-creator problem, can’t download fedora 13 direct from the app.

I’ve installed liveusb-creator prior to a Fedora release party where we will provide people the possibility to install fedora 13 on their usb stick. I didn’t have any live cd iso so I tried to select the “Download Fedora” option, but I was surprised to see that there’s not option to install Fedora 13. So here’s the workaround.

Edit the file /usr/lib/python2.6/site-packages/liveusb/releases.py

# vim /usr/lib/python2.6/site-packages/liveusb/releases.py

and add those line:

{
 'name': 'Fedora 13 (i686)',
 'url': 'http://download.fedora.redhat.com/pub/fedora/linux/releases/13/Live/i686/Fedora-13-i686-Live.iso',
 'sha256': '47ccc37db256387b70857f53a6067e8d50e692c9aa85e45e63e5190c5d1e0942',
 },

 {
 'name': 'Fedora 13 KDE (i686)',
 'url': 'http://download.fedora.redhat.com/pub/fedora/linux/releases/13/Live/i686/Fedora-13-i686-Live-KDE.iso',
 'sha256': '6828c02f2bce4ec3bd1ca488df8662640bf53fe7724913310295a5f5f6502cf8',
 },

 {
 'name': 'Fedora 13 (x86_64)',
 'url': 'http://download.fedora.redhat.com/pub/fedora/linux/releases/13/Live/x86_64/Fedora-13-x86_64-Live.iso',
 'sha256': 'c16923e9c2f04af3609c9534f32ea280e4d2c3af50e704344ccb35090f87065a',
 },

 {
 'name': 'Fedora 13 KDE (x86_64)',
 'url': 'http://download.fedora.redhat.com/pub/fedora/linux/releases/13/Live/x86_64/Fedora-13-x86_64-Live-KDE.iso',
 'sha256': '789d7090d39230f0e9b16ed3276974223c120db3120c48e53fa95a6f1604c650',
 },

Save this and restart liveusb-creator, you should have the option to download Fedora 13. This is a temporary workaround, untill the package get fixed.

For your information, the file has been updated few weeks ago on https://fedorahosted.org/liveusb-creator/browser/liveusb/releases.py but the packages included in Fedora 13 didn’t include this updated file. I’ve submitted the information to the maintainer, the fixed package should come soon.

@+

——-

Update :

This bug is fixed there’s an update for Fedora 13 https://admin.fedoraproject.org/updates/liveusb-creator-3.9.2-1.fc13 and Fedora 12 https://admin.fedoraproject.org/updates/liveusb-creator-3.9.2-1.fc12

Forget about the workaround, you can just update to the lastest version of the package!

Fedora 13 – Evolution problem – Program terminated with signal 6, Aborted. or [abrt] crash in evolution-2.30.1-5.fc13: malloc_consolidate: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)

After the installation of Fedora13 finished on my laptop. I started to restore files, email accounts etc… Everything worked well untill I restored my evolution backup. Evolution was really unstable, I mean I was away from the keyboard and it was crashing. I was unable to read/write any email..

So I reported a bug on the redhat bugzilla using ABRT the tool in fedora, it detect when something crash and offer you to report the bug and send a backtrace here’s the bug report: https://bugzilla.redhat.com/show_bug.cgi?id=596916

So Evolution was crashing with message like this:

crash  in evolution-2.30.1-5.fc13: malloc_consolidate: Process  /usr/bin/evolution was killed by signal 11 (SIGSEGV)
or
Program terminated with signal 6, Aborted.

I’ve talked with folks from Fedora project and nobody seems to have big problem with Evolution. So I started to look what’s wrong with my install! First, I started evolution in a shell to see the output… Here’s the result I got:

[rpurcell@t61ig ~]$ evolution
(evolution:15208): e-data-server-DEBUG: Loading categories from "/home/rpurcell/.evolution/categories.xml"
(evolution:15208): e-data-server-DEBUG: Loaded 31 categories

Untill here Evolution work fine. And…

bbdb: Buddy list has changed since last sync.
bbdb: Synchronizing buddy list to contacts...
bbdb: Done syncing buddy list to contacts.
*** glibc detected *** evolution: corrupted double-linked list: 0x09c873a0 ***
======= Backtrace: =========
/lib/libc.so.6(+0x7511e1)[0xe851e1]
/lib/libc.so.6(+0x7539b3)[0xe879b3]
/lib/libglib-2.0.so.0(g_free+0x37)[0xd57ff7]
/usr/lib/evolution/2.30/plugins/liborg-gnome-evolution-bbdb.so(+0x454a)[0x2f5c54a]
/lib/libglib-2.0.so.0(g_list_foreach+0x27)[0xd4cc17]
/usr/lib/evolution/2.30/plugins/liborg-gnome-evolution-bbdb.so(+0x4724)[0x2f5c724]
/usr/lib/evolution/2.30/plugins/liborg-gnome-evolution-bbdb.so(+0x4a30)[0x2f5ca30]
/lib/libglib-2.0.so.0(+0x944210)[0xd7a210]
/lib/libpthread.so.0[0x876919]
/lib/libc.so.6(clone+0x5e)[0xef3e5e]

[…]

I’ve cut some text.. But the important part is that once evolution start to sync the buddy list contact, it crashed.. So I removed the option from the preference menu => Mail preferences => Synchronize contact info and images from Pidgin buddy lists.

And voila! No more crash, Evolution is rock stable…

So if you have the same problem with your evolution on Fedora13, and this option is activated, disable this!! And if this fix your problem please post it on the bug report!

@++