We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
phpMyAdmin Status - Wrong Date
phpMyAdmin Status - Wrong Date
Hello,
After the initial install of VestaCP, I changed the timezone of the system. As a result, some elements of my websites are showing with the correct new date and some are still using the old one. I checked the database with "select now();" and the result is the correct new date. However, during the check, I noticed the following output from mysql:
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 2351
Current database: *** NONE ***
Should I worry about it?
Also, even though the returned result was the correct new timeszone, when I go to phpMyAdmin under the Status tab, the line where it shows when the mysql was started is the old/wrong timezone.
Please suggest where to look.
Thanks.
After the initial install of VestaCP, I changed the timezone of the system. As a result, some elements of my websites are showing with the correct new date and some are still using the old one. I checked the database with "select now();" and the result is the correct new date. However, during the check, I noticed the following output from mysql:
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 2351
Current database: *** NONE ***
Should I worry about it?
Also, even though the returned result was the correct new timeszone, when I go to phpMyAdmin under the Status tab, the line where it shows when the mysql was started is the old/wrong timezone.
Please suggest where to look.
Thanks.
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: phpMyAdmin Status - Wrong Date
Changing timezone should not have any impact over running services... yes the CRON jobs may fire at the wrong times.
MySQL issue is something else, check your logs and identify what killed mysql service.
Also, telling about your OS and server configuration is also helpful in getting right guidance.
MySQL issue is something else, check your logs and identify what killed mysql service.
Also, telling about your OS and server configuration is also helpful in getting right guidance.
Re: phpMyAdmin Status - Wrong Date
Actually the MYSQL server is not stopped. It is running just fine and the websites doesn't have issues. It is just that when I execute the command on MYSQL shell, it provides that output which is a bit worrying. Why would the server report to not being running while it is?
Server version: Apache/2.2.15 (Unix)
Server built: Nov 15 2012 15:52:50
nginx version: nginx/1.10.0
Server version: 5.5.49 MySQL Community Server (GPL) by Remi
PHP 5.4.45 (cli) (built: Apr 27 2016 10:36:34)
CentOS 6.7 64bit
Server version: Apache/2.2.15 (Unix)
Server built: Nov 15 2012 15:52:50
nginx version: nginx/1.10.0
Server version: 5.5.49 MySQL Community Server (GPL) by Remi
PHP 5.4.45 (cli) (built: Apr 27 2016 10:36:34)
CentOS 6.7 64bit
Re: phpMyAdmin Status - Wrong Date
* change your server time - make sync with ntp-server
* php.ini - add date.timezone
By default:
* php.ini - add date.timezone
By default:
Code: Select all
; Defines the default timezone used by the date functions
; http://php.net/date.timezone
;date.timezone =