I can no longer view the contents of a message. I click the blue icon to bring up message details and that is fine when I scroll down to quarantine and click the message path ex. /nonspam/EB06C20049.ADA15 it opens viewmail.php but there is no message. Before it used to show the plaintext and html version and now nothing.
Where should I be looking to figure out what happened?
Cannot View Message Content
Re: Cannot View Message Content
1. Did you check the log(s) for issues, as you had some issues after the 3.0.2.5 -> 3.0.2.6 update
2. Just one message or all messages
2. Just one message or all messages
“We are stuck with technology when what we really want is just stuff that works.” -Douglas Adams
Re: Cannot View Message Content
im monitoring /var/logs/httpd/error_log and there is nothing in there except for an error about the php.ini file when i logout of mailwatch. also checking /var/log/messages and there is nothing in there from sql
This is happening for all my messages including ones that previously worked.
This is happening for all my messages including ones that previously worked.
Re: Cannot View Message Content
Also checked the and the mysql log ( in /var/log or /var/lib/mysql)?
As I remember well you did install 3.0.2.5 and upgraded to 3.0.2.6. on Nov 29 and had some config issues and self-signed certificate issues.
Code: Select all
/var/log/httpd/ssl_error_log
What do you mean with: previously ?This is happening for all my messages including ones that previously worked.
As I remember well you did install 3.0.2.5 and upgraded to 3.0.2.6. on Nov 29 and had some config issues and self-signed certificate issues.
“We are stuck with technology when what we really want is just stuff that works.” -Douglas Adams
Re: Cannot View Message Content
Thank you for your assistance,
yes 3.0.2.5 to 3.0.2.6 there were issues but i resolved them and i got my certificate issues fixed as well. currently using my wildcard certificate for ssl and tls over smtp. after the upgrade to 3.0.2.6 i could view message contents for a week or so, then in my quest to further tune my settings is when i lost my ability to view message contents.
/var/log/httpd/error_log:
[Mon Jan 14 18:11:40 2019] [notice] Apache/2.2.15 (Unix) mod_fcgid/2.3.9 PHP/7.2.12 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured -- resuming normal operations
[Mon Jan 14 18:55:12 2019] [notice] Graceful restart requested, doing restart
[Mon Jan 14 18:55:12 2019] [notice] Digest: generating secret for digest authentication ...
[Mon Jan 14 18:55:12 2019] [notice] Digest: done
[Mon Jan 14 18:55:13 2019] [notice] Apache/2.2.15 (Unix) mod_fcgid/2.3.9 PHP/7.2.12 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured -- resuming normal operations
/var/log/httpd/ssl_error_log:
[Mon Jan 14 17:51:57 2019] [warn] [client 10.0.20.1] PHP Warning: ini_set(): A session is active. You cannot change the session module's ini settings at this time in /var/www/html/mailscanner/logout.php on line 40, referer: https://mail.cityofmontclair.org/mailscanner/status.php
[Mon Jan 14 18:18:48 2019] [warn] [client 10.0.20.1] PHP Warning: ini_set(): A session is active. You cannot change the session module's ini settings at this time in /var/www/html/mailscanner/logout.php on line 40, referer: https://mail.cityofmontclair.org/mailsc ... 10ED.AC5AE
[Mon Jan 14 18:20:34 2019] [notice] [client 10.0.20.1] PHP Notice: Undefined offset: 0 in /var/www/html/mailscanner/filter.inc.php on line 127, referer: https://mail.cityofmontclair.org/mailsc ... eports.php
[Mon Jan 14 18:20:34 2019] [notice] [client 10.0.20.1] PHP Notice: Undefined offset: 0 in /var/www/html/mailscanner/filter.inc.php on line 128, referer: https://mail.cityofmontclair.org/mailsc ... eports.php
[Mon Jan 14 18:20:34 2019] [notice] [client 10.0.20.1] PHP Notice: Undefined offset: 0 in /var/www/html/mailscanner/filter.inc.php on line 129, referer: https://mail.cityofmontclair.org/mailsc ... eports.php
[Mon Jan 14 18:36:57 2019] [warn] [client 10.0.20.1] PHP Warning: ini_set(): A session is active. You cannot change the session module's ini settings at this time in /var/www/html/mailscanner/logout.php on line 40, referer: https://mail.cityofmontclair.org/
/var/log/mysqld.log: {empty}
/var/lib/mysql/mail.cityofmontclair.org.err:
2019-01-14 18:10:12 140583621880576 [Note] /usr/sbin/mysqld: Normal shutdown
2019-01-14 18:10:12 140583621880576 [Note] Event Scheduler: Purging the queue. 0 events
2019-01-14 18:10:12 140582936610560 [Note] InnoDB: FTS optimize thread exiting.
2019-01-14 18:10:12 140583621880576 [Note] InnoDB: Starting shutdown...
2019-01-14 18:10:13 140583621880576 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
2019-01-14 18:10:14 140583621880576 [Note] InnoDB: Shutdown completed; log sequence number 50064233681
2019-01-14 18:10:14 140583621880576 [Note] /usr/sbin/mysqld: Shutdown complete
190114 18:10:14 mysqld_safe mysqld from pid file /var/lib/mysql/mail.cityofmontclair.org.pid ended
190114 18:11:28 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2019-01-14 18:11:29 140390201047072 [Note] /usr/sbin/mysqld (mysqld 10.1.37-MariaDB) starting as process 1778 ...
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: The InnoDB memory heap is disabled
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Using Linux native AIO
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Using SSE crc32 instructions
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Completed initialization of buffer pool
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Highest supported file format is Barracuda.
2019-01-14 18:11:30 140390201047072 [Note] InnoDB: 128 rollback segment(s) are active.
2019-01-14 18:11:30 140390201047072 [Note] InnoDB: Waiting for purge to start
2019-01-14 18:11:30 140390201047072 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.41-84.1 started; log sequence number 50064233681
2019-01-14 18:11:30 140390201047072 [Note] Plugin 'FEEDBACK' is disabled.
2019-01-14 18:11:30 140389388379904 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-01-14 18:11:30 140390201047072 [Note] Server socket created on IP: '::'.
2019-01-14 18:11:30 140390201047072 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.1.37-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
2019-01-14 19:28:32 7faef77f8700 InnoDB: FTS Optimize Removing table mailscanner/#sql2-6f2-194
2019-01-15 03:47:45 7faef77f8700 InnoDB: FTS Optimize Removing table mailscanner/#sql2-6f2-529
2019-01-16 04:03:57 7faef77f8700 InnoDB: FTS Optimize Removing table mailscanner/#sql2-6f2-1e1a
yes 3.0.2.5 to 3.0.2.6 there were issues but i resolved them and i got my certificate issues fixed as well. currently using my wildcard certificate for ssl and tls over smtp. after the upgrade to 3.0.2.6 i could view message contents for a week or so, then in my quest to further tune my settings is when i lost my ability to view message contents.
/var/log/httpd/error_log:
[Mon Jan 14 18:11:40 2019] [notice] Apache/2.2.15 (Unix) mod_fcgid/2.3.9 PHP/7.2.12 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured -- resuming normal operations
[Mon Jan 14 18:55:12 2019] [notice] Graceful restart requested, doing restart
[Mon Jan 14 18:55:12 2019] [notice] Digest: generating secret for digest authentication ...
[Mon Jan 14 18:55:12 2019] [notice] Digest: done
[Mon Jan 14 18:55:13 2019] [notice] Apache/2.2.15 (Unix) mod_fcgid/2.3.9 PHP/7.2.12 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured -- resuming normal operations
/var/log/httpd/ssl_error_log:
[Mon Jan 14 17:51:57 2019] [warn] [client 10.0.20.1] PHP Warning: ini_set(): A session is active. You cannot change the session module's ini settings at this time in /var/www/html/mailscanner/logout.php on line 40, referer: https://mail.cityofmontclair.org/mailscanner/status.php
[Mon Jan 14 18:18:48 2019] [warn] [client 10.0.20.1] PHP Warning: ini_set(): A session is active. You cannot change the session module's ini settings at this time in /var/www/html/mailscanner/logout.php on line 40, referer: https://mail.cityofmontclair.org/mailsc ... 10ED.AC5AE
[Mon Jan 14 18:20:34 2019] [notice] [client 10.0.20.1] PHP Notice: Undefined offset: 0 in /var/www/html/mailscanner/filter.inc.php on line 127, referer: https://mail.cityofmontclair.org/mailsc ... eports.php
[Mon Jan 14 18:20:34 2019] [notice] [client 10.0.20.1] PHP Notice: Undefined offset: 0 in /var/www/html/mailscanner/filter.inc.php on line 128, referer: https://mail.cityofmontclair.org/mailsc ... eports.php
[Mon Jan 14 18:20:34 2019] [notice] [client 10.0.20.1] PHP Notice: Undefined offset: 0 in /var/www/html/mailscanner/filter.inc.php on line 129, referer: https://mail.cityofmontclair.org/mailsc ... eports.php
[Mon Jan 14 18:36:57 2019] [warn] [client 10.0.20.1] PHP Warning: ini_set(): A session is active. You cannot change the session module's ini settings at this time in /var/www/html/mailscanner/logout.php on line 40, referer: https://mail.cityofmontclair.org/
/var/log/mysqld.log: {empty}
/var/lib/mysql/mail.cityofmontclair.org.err:
2019-01-14 18:10:12 140583621880576 [Note] /usr/sbin/mysqld: Normal shutdown
2019-01-14 18:10:12 140583621880576 [Note] Event Scheduler: Purging the queue. 0 events
2019-01-14 18:10:12 140582936610560 [Note] InnoDB: FTS optimize thread exiting.
2019-01-14 18:10:12 140583621880576 [Note] InnoDB: Starting shutdown...
2019-01-14 18:10:13 140583621880576 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
2019-01-14 18:10:14 140583621880576 [Note] InnoDB: Shutdown completed; log sequence number 50064233681
2019-01-14 18:10:14 140583621880576 [Note] /usr/sbin/mysqld: Shutdown complete
190114 18:10:14 mysqld_safe mysqld from pid file /var/lib/mysql/mail.cityofmontclair.org.pid ended
190114 18:11:28 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2019-01-14 18:11:29 140390201047072 [Note] /usr/sbin/mysqld (mysqld 10.1.37-MariaDB) starting as process 1778 ...
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: The InnoDB memory heap is disabled
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Using Linux native AIO
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Using SSE crc32 instructions
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Completed initialization of buffer pool
2019-01-14 18:11:29 140390201047072 [Note] InnoDB: Highest supported file format is Barracuda.
2019-01-14 18:11:30 140390201047072 [Note] InnoDB: 128 rollback segment(s) are active.
2019-01-14 18:11:30 140390201047072 [Note] InnoDB: Waiting for purge to start
2019-01-14 18:11:30 140390201047072 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.41-84.1 started; log sequence number 50064233681
2019-01-14 18:11:30 140390201047072 [Note] Plugin 'FEEDBACK' is disabled.
2019-01-14 18:11:30 140389388379904 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-01-14 18:11:30 140390201047072 [Note] Server socket created on IP: '::'.
2019-01-14 18:11:30 140390201047072 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.1.37-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
2019-01-14 19:28:32 7faef77f8700 InnoDB: FTS Optimize Removing table mailscanner/#sql2-6f2-194
2019-01-15 03:47:45 7faef77f8700 InnoDB: FTS Optimize Removing table mailscanner/#sql2-6f2-529
2019-01-16 04:03:57 7faef77f8700 InnoDB: FTS Optimize Removing table mailscanner/#sql2-6f2-1e1a
Re: Cannot View Message Content
Besides the php warnings, Mysql.log shows some issues.
To get a better picture, take a look at viewtopic.php?t=3157
About the FTS ( Full text index) take a look at: viewtopic.php?t=2827
The next step would be to look at the php warnings.
Installing mysql tuner and run it will help a lot to solve it. See links below.2019-01-14 19:28:32 7faef77f8700 InnoDB: FTS Optimize Removing table mailscanner/#sql2-6f2-194
2019-01-15 03:47:45 7faef77f8700 InnoDB: FTS Optimize Removing table mailscanner/#sql2-6f2-529
2019-01-16 04:03:57 7faef77f8700 InnoDB: FTS Optimize Removing table mailscanner/#sql2-6f2-1e1a
To get a better picture, take a look at viewtopic.php?t=3157
About the FTS ( Full text index) take a look at: viewtopic.php?t=2827
The next step would be to look at the php warnings.
“We are stuck with technology when what we really want is just stuff that works.” -Douglas Adams
Re: Cannot View Message Content
Hello,
have you solve this issue?
same issue here, verified all log mentonied in this 3d, nothing can help with this issue.
have you solve this issue?
same issue here, verified all log mentonied in this 3d, nothing can help with this issue.
Re: Cannot View Message Content
Try to see if the files in
are empty, if so just delete them.
and then reboot.
Code: Select all
/var/www/html/mailscanner/temp/GeoIP*
and then reboot.
Re: Cannot View Message Content
This work fine, thank you, first of all.w_bufffet wrote: ↑23 Jan 2019 19:02 Try to see if the files inare empty, if so just delete them.Code: Select all
/var/www/html/mailscanner/temp/GeoIP*
and then reboot.
But if I update again "Update GeoIP Database" under "tools and link", again I can't see anything when I click on "i" for message content.
EFA can work without this upgrade?
Re: Cannot View Message Content
Do not update!But if I update again "Update GeoIP Database" under "tools and link", again
As GeoIp provides usefull info, to get a recent copy of the GeoIP files: viewtopic.php?t=3311
“We are stuck with technology when what we really want is just stuff that works.” -Douglas Adams