Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
log spam: obexd_server_init failed
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
dewhite
Tux's lil' helper
Tux's lil' helper


Joined: 16 Mar 2003
Posts: 78
Location: Houston, Texas, USA

PostPosted: Mon Oct 17, 2016 5:37 am    Post subject: log spam: obexd_server_init failed Reply with quote

I just completed a new install earlier today and set about getting Plasma installed with all my favorite apps & utilities.

I was piddling around with filelight and noticed that before the end of day 1, my /var/log was already near 4gb. It turns out that two of the log files contained there were each passing 1.9gb, filled, entirely, with a repeating two-line spam about obexd failing to start.

The log files /var/log/daemon.log and /var/log/syslog are each overflowing with the following:

Code:
Oct 17 00:30:25 localhost obexd[32385]: OBEX daemon 5.39
Oct 17 00:30:25 localhost obexd[32385]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32387]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32387]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32389]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32389]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32391]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32391]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32393]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32393]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32395]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32395]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32397]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32397]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32399]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32399]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32401]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32401]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32403]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32403]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32405]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32405]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32407]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32407]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32409]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32409]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32411]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32411]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32413]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32413]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32415]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32415]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32419]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32419]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32423]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32423]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32425]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32425]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32427]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32427]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32429]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32429]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32431]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32431]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32433]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32433]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32435]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32435]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32437]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32437]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32439]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32439]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32441]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32441]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32451]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32451]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32453]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32453]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32455]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32455]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32457]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32457]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32459]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32459]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32461]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32461]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32466]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32466]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32469]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32469]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32471]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32471]: obex_server_init failed
Oct 17 00:30:26 localhost obexd[32473]: OBEX daemon 5.39
Oct 17 00:30:26 localhost obexd[32473]: obex_server_init failed
Oct 17 00:30:27 localhost obexd[32475]: OBEX daemon 5.39
Oct 17 00:30:27 localhost obexd[32475]: obex_server_init failed


As you can see, the message is being posted to each log several times each second.

Code:
ps -aux | grep obex
gives no process for this daemon so I'm guessing it must be a function of some larger process. A google search indicates that obexd might have something to do with bluetooth - this is a desktop system with no bluetooth module attached.

Any ideas on what's run amok and how/where to see about shutting it up?

Happy to provide any additional details about system specs or configuration upon request - thanks!
_________________
Work WS: R7-1700x | 2x8Gb DDR4 | GT1030 | 275Gb & 1Tb SSD Root/Home
Work FS: i5-6500 | 8Gb DDR4 | 275Gb SSD | 3x 1TB RAID5
Home WS: NUC7i5BNH | 2x8Gb DDR4 | 275Gb SSD (running ARCH Linux)
Home FS: FX-8320e | 8Gb DDR3 | 8400GS | 4x 5TB RAID5


Last edited by dewhite on Mon Oct 17, 2016 6:00 am; edited 1 time in total
Back to top
View user's profile Send private message
dewhite
Tux's lil' helper
Tux's lil' helper


Joined: 16 Mar 2003
Posts: 78
Location: Houston, Texas, USA

PostPosted: Mon Oct 17, 2016 5:57 am    Post subject: Reply with quote

Looking further at the output of filelight I also now see that the .xsession-errors file for my user is ridiculously huge at just over 800mb (again, just about 12 hours into the life of this young system). That file is filed with more complaints about obexd which must be a part of bluedevil:

Code:
bluedevil: ObexManager operational changed false
bluedevil: ObexManager operational changed false
bluedevil: ObexManager operational changed false
bluedevil: ObexManager operational changed false
bluedevil: ObexManager operational changed false


I'm assuming that bluedevil was probably installed along with plasma-meta or kde-apps-meta?
_________________
Work WS: R7-1700x | 2x8Gb DDR4 | GT1030 | 275Gb & 1Tb SSD Root/Home
Work FS: i5-6500 | 8Gb DDR4 | 275Gb SSD | 3x 1TB RAID5
Home WS: NUC7i5BNH | 2x8Gb DDR4 | 275Gb SSD (running ARCH Linux)
Home FS: FX-8320e | 8Gb DDR3 | 8400GS | 4x 5TB RAID5
Back to top
View user's profile Send private message
dewhite
Tux's lil' helper
Tux's lil' helper


Joined: 16 Mar 2003
Posts: 78
Location: Houston, Texas, USA

PostPosted: Mon Oct 17, 2016 6:30 am    Post subject: Reply with quote

Found a temporary fix to shut this unruly process up:

Within Plasma: Open System Settings. Go to "Startup and Shutdown" under "Workspace." Select "Background Services." Deselect use of Service called "Bluetooth." Apply Changes. Reboot system (or as I did) restart your xdm session.

This brings a stop to the spam to both log files and the .xsession-errors file.

I'm still curious what brings on this behavior - if it is a bug or something unique to the way that I installed my system. If this is a widespread bug, it should be messing up people's systems left & right...
_________________
Work WS: R7-1700x | 2x8Gb DDR4 | GT1030 | 275Gb & 1Tb SSD Root/Home
Work FS: i5-6500 | 8Gb DDR4 | 275Gb SSD | 3x 1TB RAID5
Home WS: NUC7i5BNH | 2x8Gb DDR4 | 275Gb SSD (running ARCH Linux)
Home FS: FX-8320e | 8Gb DDR3 | 8400GS | 4x 5TB RAID5
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 14071

PostPosted: Tue Oct 18, 2016 1:41 am    Post subject: Reply with quote

I would consider it a bug that the program spammed your log files like that. It may be a rare bug, but it should have required some very explicit action from you to put it into such an aggressive restart & report loop. Since you did not mention taking such an action, it is apparently looping like that without instruction from the user, which I consider to be poor practice.
Back to top
View user's profile Send private message
dewhite
Tux's lil' helper
Tux's lil' helper


Joined: 16 Mar 2003
Posts: 78
Location: Houston, Texas, USA

PostPosted: Tue Oct 18, 2016 7:44 pm    Post subject: Reply with quote

Hu wrote:
I would consider it a bug that the program spammed your log files like that. It may be a rare bug, but it should have required some very explicit action from you to put it into such an aggressive restart & report loop. Since you did not mention taking such an action, it is apparently looping like that without instruction from the user, which I consider to be poor practice.


Exactly my concern. I can think of no deviant action during my install that should have allowed this behavior. Can you suggest the most appropriate action to take to escalate this concern? I often scan through bug submissions to solve my own problems, but I've never filed one myself related to Gentoo.
_________________
Work WS: R7-1700x | 2x8Gb DDR4 | GT1030 | 275Gb & 1Tb SSD Root/Home
Work FS: i5-6500 | 8Gb DDR4 | 275Gb SSD | 3x 1TB RAID5
Home WS: NUC7i5BNH | 2x8Gb DDR4 | 275Gb SSD (running ARCH Linux)
Home FS: FX-8320e | 8Gb DDR3 | 8400GS | 4x 5TB RAID5
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 14071

PostPosted: Wed Oct 19, 2016 1:22 am    Post subject: Reply with quote

You can file it with Gentoo at bugs.gentoo.org or you could try to escalate directly to upstream. Either way, you will likely be asked to provide debugging data. The respondent should be able to instruct you on how to collect this. The messages it spewed so far are unlikely to be helpful.
Back to top
View user's profile Send private message
Ctp.Slow
n00b
n00b


Joined: 30 Oct 2016
Posts: 1

PostPosted: Sun Oct 30, 2016 9:57 pm    Post subject: Reply with quote

Hey all,

I had the same problem today with a new installation. The problem was that the bluetooth service wasn't started. After this everything went to normal.

I agree that the behavior of spamming the logs is not the fine way to handle this situation. There should be some appropriate error handling.

Cheers :)
Back to top
View user's profile Send private message
trigggl
Apprentice
Apprentice


Joined: 26 Aug 2007
Posts: 234
Location: Arkansas

PostPosted: Mon Jan 22, 2018 8:05 pm    Post subject: Reply with quote

This just helped me out with a recent plasma install.
_________________
Greg
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum