Open GM-MG opened 3 years ago
We working under fiix
Vesta 1.0.0 Relase 3
DB -> phpMyAdmin -> open with http (vesta is on https)
Thanks GM-MG, SSL generating now working. But not work restart from admin interface.
Log clean but only: fpm-php.log PHP Notice: Undefined variable: users in /usr/local/vesta/web/api/v1/login/index.php on line 163 PHP Notice: Undefined variable: error in /usr/local/vesta/web/api/v1/login/index.php on line 167
Server -> Restart Backup -> Create Backup On Release 3 - works.
Thanks great support :-), now we haven't encountered any problem yet, so I'll let you know :-) thank you.
Thanks GM-MG, SSL generating now working. But not work restart from admin interface.
Log clean but only: fpm-php.log PHP Notice: Undefined variable: users in /usr/local/vesta/web/api/v1/login/index.php on line 163 PHP Notice: Undefined variable: error in /usr/local/vesta/web/api/v1/login/index.php on line 167
What OS and web stack on your server
OS Ubuntu Server 18.04 LTS
Web stack apache+nginx or nginx + php-fpm ?
Ah, yes apache+nginx , php - v - Zend OPcache v7.2.24, nginx as reverse proxy.
Ok, thank you. We will check this issue and fix it
Thanks, i now shutdown vesta FTP via admin panel and cant stop process, mysql in list/server/ apache2, nginx too - i check logs and post it.
I think it's a bug. Try to stop another services
Logs from /usr/local/vesta/log
fpm-php.log 11:45:41 UTC] PHP Warning: Invalid argument supplied for foreach() in /usr/local/vesta/web/api/v1/login/index.php on line 129 [01-Nov-2021 11:45:42 UTC] PHP Notice: Undefined variable: error in /usr/local/vesta/web/api/v1/login/index.php on line 167
nginx-error.log - ok system.log - ok letsencrypt.log -ok letsencrypt_cron.log -ok error.log : 2021-11-01 12:50:02 v-update-sys-rrd-mysql 'daily' [Error 15] backup.log - ok normal
/var/log/apache2
[Mon Nov 01 12:11:24.572494 2021] [mpm_prefork:notice] [pid 18149] AH00169: caught SIGTERM, shutting down [Mon Nov 01 12:12:31.655523 2021] [suexec:notice] [pid 809] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec) [Mon Nov 01 12:12:41.284452 2021] [:notice] [pid 1281] mod_ruid2/0.9.8 enabled [Mon Nov 01 12:12:41.293020 2021] [mpm_prefork:notice] [pid 1281] AH00163: Apache/2.4.29 (Ubuntu) mod_fcgid/2.3.9 OpenSSL/1.1.1 configured -- resuming normal operations [Mon Nov 01 12:12:41.293059 2021] [core:notice] [pid 1281] AH00094: Command line: '/usr/sbin/apache2' [Mon Nov 01 12:45:29.811430 2021] [mpm_prefork:notice] [pid 1281] AH00169: caught SIGTERM, shutting down
/var/log/mysql
[Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).-ok
in list server in VestaCP i see " screen" if click mysql stop :
on cli : ● mysql.service - MySQL Community Server Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: en Active: inactive (dead) since Mon 2021-11-01 12:59:14 CET; 9s ago -- so definitly - stoped but in interface only see 0 MB, ok so can kill from vestaCP list servers ( mysql ) but may be need color diference - as stopped.
/var/log/apache2 ( test stop, restart via vesta interface ) working but ..
but I don't see color differentiation that the service is stopped, I find only out via comand line eg service apache2 status, ideally if it was marked in the interface that apache2 is due.
[Mon Nov 01 13:09:26.899802 2021] [suexec:notice] [pid 30604] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec) [Mon Nov 01 13:09:26.939468 2021] [:notice] [pid 30605] mod_ruid2/0.9.8 enabled [Mon Nov 01 13:09:26.943861 2021] [mpm_prefork:notice] [pid 30605] AH00163: Apache/2.4.29 (Ubuntu) mod_fcgid/2.3.9 OpenSSL/1.1.1 configured -- resuming normal operations [Mon Nov 01 13:09:26.943904 2021] [core:notice] [pid 30605] AH00094: Command line: '/usr/sbin/apache2'
I think it's a bug. Try to stop another services
Its ok but same color, i must check service via comand line if working or no. :-) in vesta interface have same color as running servicies, may be need same mechanism as old vesta - grey - not work, white - online, working :-)
Stop servicies from vesta list servers - working but " colors " make me mad, at first glance, it was not clear whether the service was running or not, the only option is to click elsewhere, for example on "WEB" and then back to the list servers and look at the CPU in% and RAM .. or via the CLI (eg service mysql status, etc ..) Previously it was gray - in gray when the service turned out it was easier to recognize that it was not working or was going out.
Vesta 1.0.0 Relase 3
DB -> phpMyAdmin -> open with http (vesta is on https)
Vesta 1.0.0 Release 4 1) still no https on link to phpMyAdmin 2) iptables & fail2ban stay to "Uptime: 0 Minutes"
What OS on your server ?
What OS on your server ?
CentOS 7
Thank you
Before update: http to phpmyadmin, same with webmail (vesta is on https) Server Restart didn't show the last message (fix with: "sleep 5" before "/sbin/reboot")
After update doesn't work: Manual Backup Server Restart iptables & fail2ban stay (again) to "Uptime: 0 Minutes"