-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
SOME FACTS:
Having been in the IRC #mythtv-users chat when 0.25 first released
there were a number of reports of it segfaulting for things like no
database connection and such when it should have generated an error
message through error handling. Several of the "developers" responded
that this was known and being addressed.
A THEORY:
Add to this the atrpms issue with yum not identifying the libmyth*
name changes that occurred from 0.24 to 0.25-283 and with 0.25-283 to
0.25-285 and I and several others appear to have run a mixed version
mythtv without realizing that was what we had "butchered" our way
into. I've had 0.25-285 running now for three days straight and not a
single segfault in /var/log/messages.
A TOOL:
I am sure there are others, but I ran this script in the file
/etc/cron.hourly/chkmythbackend.sh to handle potential segfaults to
the backend.
[quote]
#!/bin/sh
SERVICE=mythbackend;
RESULT=$(service $SERVICE status | grep -o running)
if [ "$RESULT" = "running" ] ;
then
# echo "$SERVICE service running, everything is fine" >> /var/log/cron
else
# echo "$SERVICE is not running, will start it again" >> /var/log/cron
service $SERVICE start >> /var/log/cron
fi
[/quote]
Sincerely,
Bob Lightfoot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPjcDAAAoJEKqgpLIhfz3XmEgH/Au1Mfm4Yhom05+CMr1QEF2N
SWBAqPTgjb6nfJhtJHNHHIhCkP9h9mf59460prM3basjKY2Er2rMsGyYkBJejkJu
eQHfttCJd9q7ihwrliStWOYrN6bKjMkodo3onk9OwM4zS6r5STJZFqyYDlYZbm1U
+rUWboIaiapQA/Ryr4NE4zG6YTlEJcDMjlvUNVu84t5gochFQXc5Gbn/lQRM6rDG
tqd55TL62YABnbg8X3SKq6Fu7ainF94CtaOQRN1jg9bdGDQQRplfan4U5GWqcjEp
JM5SQ67CrHx6nMt2iOqSfIm/U3MAqupVCaK0WTs++mUtslIwRScADmwo0e7I9zk=
=bU2t
-----END PGP SIGNATURE-----
_______________________________________________
atrpms-users mailing list
atrpms-users@atrpms.net
http://lists.atrpms.net/mailman/listinfo/atrpms-users
Hash: SHA1
SOME FACTS:
Having been in the IRC #mythtv-users chat when 0.25 first released
there were a number of reports of it segfaulting for things like no
database connection and such when it should have generated an error
message through error handling. Several of the "developers" responded
that this was known and being addressed.
A THEORY:
Add to this the atrpms issue with yum not identifying the libmyth*
name changes that occurred from 0.24 to 0.25-283 and with 0.25-283 to
0.25-285 and I and several others appear to have run a mixed version
mythtv without realizing that was what we had "butchered" our way
into. I've had 0.25-285 running now for three days straight and not a
single segfault in /var/log/messages.
A TOOL:
I am sure there are others, but I ran this script in the file
/etc/cron.hourly/chkmythbackend.sh to handle potential segfaults to
the backend.
[quote]
#!/bin/sh
SERVICE=mythbackend;
RESULT=$(service $SERVICE status | grep -o running)
if [ "$RESULT" = "running" ] ;
then
# echo "$SERVICE service running, everything is fine" >> /var/log/cron
else
# echo "$SERVICE is not running, will start it again" >> /var/log/cron
service $SERVICE start >> /var/log/cron
fi
[/quote]
Sincerely,
Bob Lightfoot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPjcDAAAoJEKqgpLIhfz3XmEgH/Au1Mfm4Yhom05+CMr1QEF2N
SWBAqPTgjb6nfJhtJHNHHIhCkP9h9mf59460prM3basjKY2Er2rMsGyYkBJejkJu
eQHfttCJd9q7ihwrliStWOYrN6bKjMkodo3onk9OwM4zS6r5STJZFqyYDlYZbm1U
+rUWboIaiapQA/Ryr4NE4zG6YTlEJcDMjlvUNVu84t5gochFQXc5Gbn/lQRM6rDG
tqd55TL62YABnbg8X3SKq6Fu7ainF94CtaOQRN1jg9bdGDQQRplfan4U5GWqcjEp
JM5SQ67CrHx6nMt2iOqSfIm/U3MAqupVCaK0WTs++mUtslIwRScADmwo0e7I9zk=
=bU2t
-----END PGP SIGNATURE-----
_______________________________________________
atrpms-users mailing list
atrpms-users@atrpms.net
http://lists.atrpms.net/mailman/listinfo/atrpms-users