The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
|||
|
|||
Here you are:
Code:
find / -name exim_* -print /usr/sbin/exim_dbmbuild /usr/sbin/exim_dumpdb /usr/sbin/exim_lock /usr/sbin/exim_tidydb /usr/sbin/exim_fixdb /usr/sbin/exim_convert4r4 /usr/sbin/exim_checkaccess /usr/share/man/man8/exim_fixdb.8.gz /usr/share/man/man8/exim_dumpdb.8.gz /usr/share/man/man8/exim_convert4r4.8.gz /usr/share/man/man8/exim_db.8.gz /usr/share/man/man8/exim_lock.8.gz /usr/share/man/man8/exim_checkaccess.8.gz /usr/share/man/man8/exim_tidydb.8.gz /usr/share/man/man8/exim_dbmbuild.8.gz Code:
find / -name exim4* -print /sys/fs/cgroup/pids/system.slice/exim4.service /sys/fs/cgroup/devices/system.slice/exim4.service /sys/fs/cgroup/memory/system.slice/exim4.service /sys/fs/cgroup/systemd/system.slice/exim4.service /sys/fs/cgroup/unified/system.slice/exim4.service /usr/lib/exim4 /usr/lib/exim4/exim4 /usr/sbin/exim4 /usr/share/doc/exim4-base /usr/share/doc/exim4 /usr/share/doc/exim4-daemon-light /usr/share/doc/exim4-config /usr/share/doc-base/exim4-spec-txt /usr/share/doc-base/exim4-filter-txt /usr/share/doc-base/exim4-readme-debian /usr/share/lintian/overrides/exim4-daemon-light /usr/share/lintian/overrides/exim4-config /usr/share/exim4 /usr/share/exim4/exim4_refresh_gnutls-params /usr/share/man/man5/exim4_local_sender_callout.5.gz /usr/share/man/man5/exim4_passwd_client.5.gz /usr/share/man/man5/exim4_local_rcpt_callout.5.gz /usr/share/man/man5/exim4_local_domain_dnsbl_whitelist.5.gz /usr/share/man/man5/exim4_local_host_blacklist.5.gz /usr/share/man/man5/exim4_exim_key.5.gz /usr/share/man/man5/exim4_sender_local_deny_exceptions.5.gz /usr/share/man/man5/exim4_exim_crt.5.gz /usr/share/man/man5/exim4-config_files.5.gz /usr/share/man/man5/exim4_hubbed_hosts.5.gz /usr/share/man/man5/exim4_host_local_deny_exceptions.5.gz /usr/share/man/man5/exim4_passwd.5.gz /usr/share/man/man5/exim4_local_sender_blacklist.5.gz /usr/share/man/man8/exim4.8.gz /usr/share/bug/exim4-base /usr/share/bug/exim4 /usr/share/bug/exim4-daemon-light /usr/share/bug/exim4-config /run/exim4 /run/systemd/generator.late/graphical.target.wants/exim4.service /run/systemd/generator.late/multi-user.target.wants/exim4.service /run/systemd/generator.late/exim4.service /var/lib/exim4 /var/lib/dpkg/info/exim4-config.list /var/lib/dpkg/info/exim4-base.preinst /var/lib/dpkg/info/exim4-config.postrm /var/lib/dpkg/info/exim4-daemon-light.prerm /var/lib/dpkg/info/exim4.list /var/lib/dpkg/info/exim4-base.md5sums /var/lib/dpkg/info/exim4-config.templates /var/lib/dpkg/info/exim4-daemon-light.postrm /var/lib/dpkg/info/exim4-base.templates /var/lib/dpkg/info/exim4-config.postinst /var/lib/dpkg/info/exim4-config.config /var/lib/dpkg/info/exim4-daemon-light.md5sums /var/lib/dpkg/info/exim4.md5sums /var/lib/dpkg/info/exim4.postinst /var/lib/dpkg/info/exim4-config.md5sums /var/lib/dpkg/info/exim4-base.postrm /var/lib/dpkg/info/exim4-daemon-light.list /var/lib/dpkg/info/exim4-config.conffiles /var/lib/dpkg/info/exim4-config.preinst /var/lib/dpkg/info/exim4-base.config /var/lib/dpkg/info/exim4.config /var/lib/dpkg/info/exim4-base.list /var/lib/dpkg/info/exim4-base.postinst /var/lib/dpkg/info/exim4-daemon-light.templates /var/lib/dpkg/info/exim4-base.conffiles /var/lib/dpkg/info/exim4-daemon-light.config /var/lib/dpkg/info/exim4.postrm /var/lib/dpkg/info/exim4-daemon-light.postinst /var/lib/dpkg/info/exim4.templates /var/spool/exim4 /home/log/exim4 /etc/logrotate.d/exim4-base /etc/logrotate.d/exim4-paniclog /etc/default/exim4 /etc/ppp/ip-up.d/exim4 /etc/cron.daily/exim4-base /etc/exim4 /etc/exim4/exim4.conf.template.dpkg-old /etc/exim4/exim4.conf.template /etc/init.d/exim4 |
#12
|
|||
|
|||
It appears they renamed & moved quite a bit in that OS version.
Youre gonna have to edit the config & find out where & what its naming the log files. Once you find the correct log, then you can tail the log as you test & send out an email. |
#13
|
|||
|
|||
So... as far as I can understand, there is a big mess on our server. We actually have two different versions of PHP : 5.3 and 7. And vBulletin is using 5.3 which is not supported any longer. As our server uses PHP 7 for e-mails, it doesn't do the link between vB and the mail server...
I now have to plan cascading updates for vBulletin and PHP to make things right and only then make further mail tests. I hope this will be sufficient. Sorry for the disturbance and thank you again Snakes1100 for your help! I'll post news when I get some. |
#14
|
|||
|
|||
1st, you actually need to test - 5.3 may or may not be the issue, you simply need to verify that by checking the log php is using as explained in response to the PM.
Just because someone told you 5.3 is the issue, doesnt mean its so. |
#15
|
|||
|
|||
I didn't find in php.ini where errors are loggued...
Code:
; Besides displaying errors, PHP can also log errors to locations such as a ; server-specific log, STDERR, or a location specified by the error_log ; directive found below. While errors should not be displayed on productions ; servers they should still be monitored and logging is a great way to do that. ; Default Value: Off ; Development Value: On ; Production Value: On ; http://php.net/log-errors log_errors = On Where could it be, by default ? |
#16
|
|||
|
|||
You need to find the php.ini file that your site uses, as you stated it runs 2 versions of php.
Check your phpinfo in the admincp. |
#17
|
|||
|
|||
Yes, we use PHP 5.3.29 as shown in admincp and so I checked that file:
/etc/php5/apache2/php.ini I also checked those two files: /usr/php53/lib/php.ini /usr/php56/lib/php.ini just to be sure but I found no path for an error log. Confusing... Thank you for your help! edit: here is what I find on the server: Code:
find / -name php.ini* -print find: ‘/proc/20015’: Aucun fichier ou dossier de ce type find: ‘/proc/20016’: Aucun fichier ou dossier de ce type /usr/lib/php/7.3/php.ini-development /usr/lib/php/7.3/php.ini-production.cli /usr/lib/php/7.3/php.ini-production /usr/php56/lib/php.ini /usr/php56/lib/php.ini-memcache /usr/php56/lib/php.ini-original /usr/php56/lib/php.ini-xcache /usr/php56/lib/php.ini-opcache /usr/php53/lib/php.ini /usr/php53/lib/php.ini-memcache /usr/php53/lib/php.ini-original /usr/php53/lib/php.ini-xcache /usr/php53/lib/php.ini-opcache /etc/php5/apache2/php.ini /etc/php5/cli/php.ini |
#18
|
|||
|
|||
You can set a log in the ini that the site is using to log errors, so just make a listing in:
/etc/php5/apache2/php.ini Restart apache/php if it doesnt start logging after adding it. |
#19
|
|||
|
|||
Well that doesn't work as the file is not created, even after restarting apache2.
I put this in /etc/php5/apache2/php.ini: Code:
; Besides displaying errors, PHP can also log errors to locations such as a ; server-specific log, STDERR, or a location specified by the error_log ; directive found below. While errors should not be displayed on productions ; servers they should still be monitored and logging is a great way to do that. ; Default Value: Off ; Development Value: On ; Production Value: On ; http://php.net/log-errors log_errors = On error_log = /var/log/phptesterror.log but the file /var/log/phptesterror.log doesn't exist, even after trying the diagnostic mail. |
#20
|
|||
|
|||
create it yourself
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|