Opened 14 years ago

Closed 14 years ago

#8496 closed enhancement (fixed)

Cryptic error message when no directory listed in StorageGroups on MBE exists on SBE

Reported by: crow.jamesm@… Owned by: cpinkham
Priority: minor Milestone: 0.24
Component: MythTV - General Version: 0.23-fixes
Severity: low Keywords: writeStringList, Error
Cc: Ticket locked: no

Description

I run Mythbuntu and currently have 0.23+fixes24710 installed. My MBE has three directories listed for its "Default" StorageGroup?. I setup a SBE that had no directories matching the storagegroups on the MBE. When the mythbackend process on the SBE was started I started getting "writeStringList: Error, invalid string list." errors on the SBE. There were also some socket errors on the MBE. The longer the SBE was running like this the slower the MBE got. I finally tracked down the source of the error and fixed the storage groups on the SBE. A better error message is attached as a patch against mainserver.cpp. I do not know if this is the best place for it.

Attachments (1)

mainserver.cpp.diff (438 bytes) - added by crow.jamesm@… 14 years ago.
Small logging improvement for mainserver.cpp

Download all attachments as: .zip

Change History (4)

Changed 14 years ago by crow.jamesm@…

Attachment: mainserver.cpp.diff added

Small logging improvement for mainserver.cpp

comment:1 Changed 14 years ago by cpinkham

Owner: changed from Isaac Richards to cpinkham
Status: newassigned

comment:2 Changed 14 years ago by robertm

Milestone: 0.23-fixes0.24

comment:3 Changed 14 years ago by cpinkham

Resolution: fixed
Status: assignedclosed

(In [26284]) Add in a debug message for better informing the use if there are no valid Storage Group directories configured for the backend. When this happens, a "writeStringList: Error, invalid string list." error ends up getting printed, but the user has no idea why. This fix prints a message right before that informing the user that they need to properly configure their Storage Groups.

Closes #8496 using patch by James Crow.

Note: See TracTickets for help on using tickets.