On Sun, January 8, 2017 5:25 pm, Alex wrote: > Hi, > > On Fri, Jan 6, 2017 at 4:13 AM, Paul Lesniewski <paul@xxxxxxxxxxxxxxxx> > wrote: >> >>> [Thu Jan 05 17:44:41.222290 2017] [:error] [pid 26909] [client >>> 174.76.81.196:61320] PHP Notice: Undefined index: ID in >>> /usr/share/squirrelmail/functions/mailbox_display.php on line 220, >>> referer: >>> https://mail.example.com/webmail/src/right_main.php?use_mailbox_cache=1&startMessage=16&mailbox=INBOX >> >> This looks a little suspicious. Some corruption or maybe a problem with >> your system's (lack of?) UID support, etc. Probably can't diagnose >> without a painful back-and-forth with echo statements. It would be at >> least more helpful if you post all the details you can concerning SM >> config, IMAP server info and config, etc. Not sure if/when I'll have >> time >> to hand-hold through debugging that kind of thing. > > It appears this message repeats "undefined index" for ID, TYPE0, > RECEIVED_DATE_STRING, RECEIVED_DATE_STRING_FULL, SUBJECT, and PRIORITY > for each client for which it occurs. The first entry appears to be > null, as in "[Fri Jan 06 14:09:04.128470 2017] [:error] [pid 22048] > [client 184.71.226.10:55890] PHP Notice: Undefined index: in > /usr/share/squirrelmail/functions/mailbox_display.php" > > Looking back, it appears this was happening before the most recent > update. Could it be a configuration problem? > >>> [Thu Jan 05 16:14:28.562424 2017] [:error] [pid 19516] [client >>> 24.66.160.94:50861] PHP Notice: Undefined offset: 63 in >>> /usr/share/squirrelmail/functions/imap_mailbox.php on line 747, >>> referer: https://mail.example.com/webmail/src/webmail.php >> >> Again, suspicious. The arrays/indexes are set up just above this to >> match. Not looking too hard at the code right now, but your mailbox >> list >> seems borked. Again, maybe your IMAP server is having issues? > > This is dovecot-2.2.27 on fedora25. Any ideas of what kind of issues > it may be having? The configuration hasn't changed in years and > there's been no specific complaints about problems with imap, through > localhost for webmail or otherwise. > >>> [Thu Jan 05 15:59:50.203093 2017] [:error] [pid 12591] [client >>> 75.149.200.52:50067] PHP Fatal error: Uncaught Error: Call to >>> undefined function eregi() in >>> /usr/share/squirrelmail/plugins/add_address/functions.php:718 >> >> What version of this plugin is installed? > > 1.0.3. The first occurrence of this error was with the most recent > svn. This did not occur with the previous version from svn, pulled > probably a year ago. That's a third party plugin. Nothing to do with SVN. I just checked and I hadn't yet got around to releasing the version that has a fix for this. >>> [Thu Jan 05 15:56:52.644892 2017] [:error] [pid 12380] [client >>> 173.10.11.217:9425] PHP Notice: Uninitialized string offset: 50 in >>> /usr/share/squirrelmail/class/mime/Rfc822Header.class.php on line 184, >>> referer: https://mail.example.com/webmail/src/right_main.php >> >> Dunno, I don't have the time to stare at the code right now, but I've >> never seen others report this, so I suspect it is particular to your >> environment or the message you are viewing. It's better to have such >> details in-hand before anyone attempts to look at this. > > This one appears to go back to 2015, occurring multiple times per day. > >>> The first error >> >> It's not an error; it's a notice > > Yes, my apologies. There are multiple warnings/notices as well as > numerous "fatal errors". > >>> is the one that seems to be most repetitive and >>> problematic. >> >> Problematic how? Please show details of side effects. > > I haven't been able to reproduce the errors/warnings myself, so I > don't really know what the end-user impact is. It's problematic in > that there are hundreds of messages in the error_log recorded per day > and I'm concerned with stability. > > Please let me know what more can be done to troubleshoot this further. POC. All configuration details. When I say suspicious, I mean that initial review makes it seem fishy that the non-plugin notices would be caused in a vanilla SM installation. So I'd need to see the message that causes the problem as well as your SM (and maybe Dovecot) configuration settings. Alternatively, try running a vanilla no-plugin SM instance (latest 1.4.23) and see if you can reproduce. If not, then change the vanilla install to be like your production install one thing at a time until you find the problem. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
