81
Installation and Upgrades / Re: cant start zentyal gui after reboot
« Last post by luis.apodaca on July 27, 2024, 12:58:11 am »hi guys
since nobody could help, i decided to get back the system using a proxmox snaptshot, that means i still dont know what happend , that why always rather solve the problem and not to avoid it but that was my only optión so far
since nobody could help, i decided to get back the system using a proxmox snaptshot, that means i still dont know what happend , that why always rather solve the problem and not to avoid it but that was my only optión so far
82
Spanish / Servicio de Radius no inicia despues de actualizar a ver 8
« Last post by luis.apodaca on July 27, 2024, 12:53:09 am »hola a todos espero puedan ayudarme
después de actualizar desde la versión 7.1.2 a la 8.0.3 el servidor Radius (único servicio en uso) ya no inicia y cada que intento a reiniciar ya sea desde shell o desde dashboard no se puede y manda errores, les dejo los mensajes de error para ver si alguien puede ayudar y de antemano agradezco cualquier ayuda
esto es la salida en el archivo de logs
command output: .
Exit value: 1 at /usr/share/perl5/EBox/Module/Service.pm line 971
EBox::Module::Service::restartService('EBox::Radius=HASH(0x561e44fe56e0)', 'restartModules', 1) called at /usr/share/perl5/EBox/Util/Init.pm line 121
eval {...} at /usr/share/perl5/EBox/Util/Init.pm line 119
EBox::Util::Init::moduleAction('radius', 'restartService', 'start') called at /usr/share/perl5/EBox/Util/Init.pm line 87
EBox::Util::Init::start at /usr/bin/zs line 35
main::main at /usr/bin/zs line 82
2024/07/26 16:25:36 INFO> Service.pm:965 EBox::Module::Service::restartService - Restarting service for module: webadmin
2024/07/26 16:25:38 INFO> Init.pm:90 EBox::Util::Init::start - Start modules finished
2024/07/26 16:26:23 INFO> Index.pm:187 EBox::Dashboard::CGI::Index::masonParameters - dashboard1
2024/07/26 16:27:27 INFO> Service.pm:965 EBox::Module::Service::restartService - Restarting service for module: radius
2024/07/26 16:27:32 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command systemctl start 'freeradius' failed.
2024/07/26 16:27:32 ERROR> Service.pm:969 EBox::Module::Service::restartService - Error restarting service: root command systemctl start 'freeradius' failed.
Error output: Job for freeradius.service failed because the control process exited with error code.
See "systemctl status freeradius.service" and "journalctl -xeu freeradius.service" for details.
Command output: .
Exit value: 1
2024/07/26 16:27:32 ERROR> Service.pm:971 EBox::Module::Service::restartService - root command systemctl start 'freeradius' failed.
2024/07/26 16:27:32 ERROR> RestartService.pm:61 EBox::SysInfo::CGI::RestartService::_process - Restart of RADIUS from dashboard failed: root command systemctl start 'freeradius' failed.
Error output: Job for freeradius.service failed because the control process exited with error code.
See "systemctl status freeradius.service" and "journalctl -xeu freeradius.service" for details.
también marca este error al intentar reiniciar desde shell
root@zentyal-radius:~# system ctl radius status
-bash: system: command not found
root@zentyal-radius:~# systemctl radius status
Unknown command verb radius.
root@zentyal-radius:~# systemctl status radius
Unit radius.service could not be found.
root@zentyal-radius:~# systemctl status freeradius
● freeradius.service - FreeRADIUS multi-protocol policy server
Loaded: loaded (/lib/systemd/system/freeradius.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2024-07-26 16:46:25 CST; 20ms ago
Docs: man:radiusd(
man:radiusd.conf(5)
http://wiki.freeradius.org/
http://networkradius.com/doc/
Process: 9925 ExecStartPre=/usr/sbin/freeradius $FREERADIUS_OPTIONS -Cx -lstdout (code=exited, status=1/FAILURE)
CPU: 57ms
root@zentyal-radius:~#
Zentyal esta en un contenedor LXC desde Proxmox 8.2.4, siempre funciono hasta que se actualizo la versión de Zentyal
gracias por cualquier ayuda
después de actualizar desde la versión 7.1.2 a la 8.0.3 el servidor Radius (único servicio en uso) ya no inicia y cada que intento a reiniciar ya sea desde shell o desde dashboard no se puede y manda errores, les dejo los mensajes de error para ver si alguien puede ayudar y de antemano agradezco cualquier ayuda
esto es la salida en el archivo de logs
command output: .
Exit value: 1 at /usr/share/perl5/EBox/Module/Service.pm line 971
EBox::Module::Service::restartService('EBox::Radius=HASH(0x561e44fe56e0)', 'restartModules', 1) called at /usr/share/perl5/EBox/Util/Init.pm line 121
eval {...} at /usr/share/perl5/EBox/Util/Init.pm line 119
EBox::Util::Init::moduleAction('radius', 'restartService', 'start') called at /usr/share/perl5/EBox/Util/Init.pm line 87
EBox::Util::Init::start at /usr/bin/zs line 35
main::main at /usr/bin/zs line 82
2024/07/26 16:25:36 INFO> Service.pm:965 EBox::Module::Service::restartService - Restarting service for module: webadmin
2024/07/26 16:25:38 INFO> Init.pm:90 EBox::Util::Init::start - Start modules finished
2024/07/26 16:26:23 INFO> Index.pm:187 EBox::Dashboard::CGI::Index::masonParameters - dashboard1
2024/07/26 16:27:27 INFO> Service.pm:965 EBox::Module::Service::restartService - Restarting service for module: radius
2024/07/26 16:27:32 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command systemctl start 'freeradius' failed.
2024/07/26 16:27:32 ERROR> Service.pm:969 EBox::Module::Service::restartService - Error restarting service: root command systemctl start 'freeradius' failed.
Error output: Job for freeradius.service failed because the control process exited with error code.
See "systemctl status freeradius.service" and "journalctl -xeu freeradius.service" for details.
Command output: .
Exit value: 1
2024/07/26 16:27:32 ERROR> Service.pm:971 EBox::Module::Service::restartService - root command systemctl start 'freeradius' failed.
2024/07/26 16:27:32 ERROR> RestartService.pm:61 EBox::SysInfo::CGI::RestartService::_process - Restart of RADIUS from dashboard failed: root command systemctl start 'freeradius' failed.
Error output: Job for freeradius.service failed because the control process exited with error code.
See "systemctl status freeradius.service" and "journalctl -xeu freeradius.service" for details.
también marca este error al intentar reiniciar desde shell
root@zentyal-radius:~# system ctl radius status
-bash: system: command not found
root@zentyal-radius:~# systemctl radius status
Unknown command verb radius.
root@zentyal-radius:~# systemctl status radius
Unit radius.service could not be found.
root@zentyal-radius:~# systemctl status freeradius
● freeradius.service - FreeRADIUS multi-protocol policy server
Loaded: loaded (/lib/systemd/system/freeradius.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2024-07-26 16:46:25 CST; 20ms ago
Docs: man:radiusd(
man:radiusd.conf(5)
http://wiki.freeradius.org/
http://networkradius.com/doc/
Process: 9925 ExecStartPre=/usr/sbin/freeradius $FREERADIUS_OPTIONS -Cx -lstdout (code=exited, status=1/FAILURE)
CPU: 57ms
root@zentyal-radius:~#
Zentyal esta en un contenedor LXC desde Proxmox 8.2.4, siempre funciono hasta que se actualizo la versión de Zentyal
gracias por cualquier ayuda
83
Installation and Upgrades / Re: DNS stopped, but starting the service disables the gui
« Last post by foeke on July 25, 2024, 02:52:08 pm »Thanks, workaround works, but had to rebootThanks. That was what was needed in the end in our case also.
84
Installation and Upgrades / Re: DNS stopped, but starting the service disables the gui
« Last post by fabio.soggia on July 24, 2024, 11:56:15 am »Thanks, workaround works, but had to reboot
85
Installation and Upgrades / Re: DNS stopped, but starting the service disables the gui
« Last post by Daniel Joven on July 24, 2024, 10:55:46 am »Hi guys,
This issue is reported in the following link, we will update it as soon as possible.
- https://github.com/zentyal/zentyal/issues/2173
This issue is reported in the following link, we will update it as soon as possible.
- https://github.com/zentyal/zentyal/issues/2173
86
Installation and Upgrades / Re: DNS stopped, but starting the service disables the gui
« Last post by fabio.soggia on July 24, 2024, 09:53:17 am »Same problem here, paid server
From log, automatic update at 3:47am (bind9-dnsutils bind9-host python3-zipp bind9-utils bind9 bind9-libs)
Now bind doens't start
From log, automatic update at 3:47am (bind9-dnsutils bind9-host python3-zipp bind9-utils bind9 bind9-libs)
Now bind doens't start
87
Installation and Upgrades / DNS stopped, but starting the service disables the gui
« Last post by foeke on July 24, 2024, 09:44:51 am »Hi,
Since this morning both paid servers stopped the DNS service. As soon as I tries to restart them, the webservice stopped (504 Gateway Time-out).
I tried to restart one server but that failed to reboot
[FAILED] Failed to start Bind Domain name server
And booting stops after [OK] Started time and date service.
The other server is still running but not working since you can’t restart the DNS and without DNS you can’t even access your fileshares.
restarting the dns using the command line didn’t work (it just halts indefinitely after the sudo zs dns restart ) same with restarting the firewall or webgui.
I've opened a ticket but I now have two customers down, so all help is appreciated.
Since this morning both paid servers stopped the DNS service. As soon as I tries to restart them, the webservice stopped (504 Gateway Time-out).
I tried to restart one server but that failed to reboot
[FAILED] Failed to start Bind Domain name server
And booting stops after [OK] Started time and date service.
The other server is still running but not working since you can’t restart the DNS and without DNS you can’t even access your fileshares.
restarting the dns using the command line didn’t work (it just halts indefinitely after the sudo zs dns restart ) same with restarting the firewall or webgui.
I've opened a ticket but I now have two customers down, so all help is appreciated.
88
Installation and Upgrades / cant start zentyal gui after reboot [SOLVED]
« Last post by luis.apodaca on July 23, 2024, 11:51:30 pm »Hi guys and thanks for any help
I recently update my zentyal virtual machine (using Proxmox 8.2.4) zentya 7.1.2 and after I reboot, the server never ends to get the user interface, i mean the ubunto desktop, so its stuck in the image of zentyal trying to get the desktop gui
Fortunely SSH access is working and apparently the RADIUS service (thats what i use zentyal for) is working but i can´t get the gui over the IP address nither in the shell from proxmox
So if SSH works then network services is working, what other services could be provoking damage ?
Im lost, what can i do for recovery mi gui and the dashboard ?
thanks in advance
I recently update my zentyal virtual machine (using Proxmox 8.2.4) zentya 7.1.2 and after I reboot, the server never ends to get the user interface, i mean the ubunto desktop, so its stuck in the image of zentyal trying to get the desktop gui
Fortunely SSH access is working and apparently the RADIUS service (thats what i use zentyal for) is working but i can´t get the gui over the IP address nither in the shell from proxmox
So if SSH works then network services is working, what other services could be provoking damage ?
Im lost, what can i do for recovery mi gui and the dashboard ?
thanks in advance
89
Portuguese / Re: 504 Gateway Time-out nginx - interface web
« Last post by juliocp1976 on July 23, 2024, 02:22:25 pm »Foi resolvido
Bug: https://github.com/zentyal/zentyal/issues/2112
Indisponibilidade do servidor http://update.zentyal.org/
Caso ocorra novamente ai tem explicação de como resolver temporariamente, pois ja aconteceu isso antes
Bug: https://github.com/zentyal/zentyal/issues/2112
Indisponibilidade do servidor http://update.zentyal.org/
Caso ocorra novamente ai tem explicação de como resolver temporariamente, pois ja aconteceu isso antes
90
Installation and Upgrades / Re: Aggiornamenti Versione 7.1
« Last post by cingo_5 on July 23, 2024, 12:50:00 pm »Ciao, oggi update.zentyal.org è tornato up