Possible bad watchdog call?
I get this when I run cron and attempt to import audio:
strtr() [function.strtr]: The second argument is not an array in /var/www/rochambeaurecords.com/modules/syslog/syslog.module on line 106.
I ran ripper.php from the command line and got a strange error about libgd (config problem on my end), but the audio still was ripped and moved with cron - but does not seem to have imported correctly. I haven't delved much into the archive module yet so I might be doing something wrong still.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | station_archive_691108.patch | 960 bytes | drewish |
Comments
Comment #1
refreshingapathy commentedRight, some serious PEBCAK error going on there, I didn't have the playlist saved before cron ran. Duh... playlist saved, and the audio is imported, however I'm getting nasty errors in the system log:
php 2010-01-21 01:33 syslog() expects parameter 1 to be long, string given in /var/www/rochambeaurecords.com/modules/syslog/syslog.module on line 79.
php 2010-01-21 01:33 strtr() [function.strtr]: The second argument is not an array in /var/www/rochambeaurecords.com/modules/syslog/syslog.module on line 106.
stationarchive 2010-01-21 01:33
php 2010-01-21 01:33 mysqli_real_escape_string() expects parameter 2 to be string, array given in /var/www/rochambeaurecords.com/includes/database.mysqli.inc on line 323.
php 2010-01-21 01:33 mysqli_real_escape_string() expects parameter 2 to be string, array given in /var/www/rochambeaurecords.com/includes/database.mysqli.inc on line 323.
php 2010-01-21 01:33 mb_strlen() expects parameter 1 to be string, array given in /var/www/rochambeaurecords.com/includes/unicode.inc on line 404.
php 2010-01-21 01:33 strtr() [function.strtr]: The second argument is not an array in /var/www/rochambeaurecords.com/modules/syslog/syslog.module on line 106.
stationarchive 2010-01-21 01:33
The module also doesn't seem to be reading the schedule - it's the only schedule created and it insists it is always recording DJ Auto Mix.
Comment #2
drewish commentedIs the archive running on the same site as the schedule?
Any way you could get a stacktrace on those syslog errors?
Comment #3
refreshingapathy commentedArchive is running on the same site as the schedule, bandwidth and disk space aren't a concern at the moment.
If you can point me to some documentation on how to obtain a stack trace on the syslog I would be more than happy to do it.
Comment #4
drewish commentedyou called it. there was one d5 style call to watchdog(). committed a fix to HEAD.
Comment #5
refreshingapathy commentedWicked. I'll apply that one later tonight to my local dev version and report back.