Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
1
Installation and Upgrades / Error output: kinit: Password incorrect
« on: January 27, 2022, 04:32:22 pm »
hello community
I have the following error. where could I look to correct it,
greetings
########
## DNS Errors on log file
########
Error output: kinit: Password incorrect
--
2021/12/23 09:37:19 ERROR> Service.pm:971 EBox::Module::Service::restartService - root command kinit -k -t /var/lib/samba/private/dns.keytab dns-zentyalplc failed.
Error output: kinit: Password incorrect
--
Exit value: 1 at root command kinit -k -t /var/lib/samba/private/dns.keytab dns-zentyalplc failed.
Error output: kinit: Password incorrect
I have the following error. where could I look to correct it,
greetings
########
## DNS Errors on log file
########
Error output: kinit: Password incorrect
--
2021/12/23 09:37:19 ERROR> Service.pm:971 EBox::Module::Service::restartService - root command kinit -k -t /var/lib/samba/private/dns.keytab dns-zentyalplc failed.
Error output: kinit: Password incorrect
--
Exit value: 1 at root command kinit -k -t /var/lib/samba/private/dns.keytab dns-zentyalplc failed.
Error output: kinit: Password incorrect
2
Installation and Upgrades / error samba
« on: April 23, 2021, 04:14:49 pm »
Hello Community
Zentyal 7.0.3.
I have the following error to the restart the samba module sought in the forum and I have not been able to solve the problem
* Restarting Zentyal module: samba [fail]
root@zentyalplc:/# tail -f /var/log/zentyal/zentyal.log
2021/04/23 10:10:53 ERROR> Service.pm:969 EBox::Module::Service::restartService - Error restarting service: Could not get ticket: could not acquire credentials using an initial credentials context: Preauthentication failed
2021/04/23 10:10:53 ERROR> Service.pm:971 EBox::Module::Service::restartService - Could not get ticket: could not acquire credentials using an initial credentials context: Preauthentication failed
at Could not get ticket: could not acquire credentials using an initial credentials context: Preauthentication failed
at /usr/share/perl5/EBox/Module/Service.pm line 971
EBox::Module::Service::restartService('EBox::Samba=HASH(0x5591da249d60)', '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('samba', 'restartService', 'restart') called at /usr/share/perl5/EBox/Util/Init.pm line 247
EBox::Util::Init::moduleRestart('samba') called at /usr/bin/zs line 62
main::main at /usr/bin/zs line 82
2021/04/23 10:10:55 INFO> SyncDaemon.pm:340 EBox::Samba::SyncDaemon::run - Samba sync daemon started
*
Rafael
Zentyal 7.0.3.
I have the following error to the restart the samba module sought in the forum and I have not been able to solve the problem
* Restarting Zentyal module: samba [fail]
root@zentyalplc:/# tail -f /var/log/zentyal/zentyal.log
2021/04/23 10:10:53 ERROR> Service.pm:969 EBox::Module::Service::restartService - Error restarting service: Could not get ticket: could not acquire credentials using an initial credentials context: Preauthentication failed
2021/04/23 10:10:53 ERROR> Service.pm:971 EBox::Module::Service::restartService - Could not get ticket: could not acquire credentials using an initial credentials context: Preauthentication failed
at Could not get ticket: could not acquire credentials using an initial credentials context: Preauthentication failed
at /usr/share/perl5/EBox/Module/Service.pm line 971
EBox::Module::Service::restartService('EBox::Samba=HASH(0x5591da249d60)', '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('samba', 'restartService', 'restart') called at /usr/share/perl5/EBox/Util/Init.pm line 247
EBox::Util::Init::moduleRestart('samba') called at /usr/bin/zs line 62
main::main at /usr/bin/zs line 82
2021/04/23 10:10:55 INFO> SyncDaemon.pm:340 EBox::Samba::SyncDaemon::run - Samba sync daemon started
*
Rafael
3
Spanish / error al restart samba
« on: April 23, 2021, 04:12:33 pm »
hola comunidad
zentyal 7.0.3
tengo el siguiente error al restart el modulo samba .he buscado en el forum y no he podido solucionar el problema
* Restarting Zentyal module: samba [fail]
root@zentyalplc:/# tail -f /var/log/zentyal/zentyal.log
2021/04/23 10:10:53 ERROR> Service.pm:969 EBox::Module::Service::restartService - Error restarting service: Could not get ticket: could not acquire credentials using an initial credentials context: Preauthentication failed
2021/04/23 10:10:53 ERROR> Service.pm:971 EBox::Module::Service::restartService - Could not get ticket: could not acquire credentials using an initial credentials context: Preauthentication failed
at Could not get ticket: could not acquire credentials using an initial credentials context: Preauthentication failed
at /usr/share/perl5/EBox/Module/Service.pm line 971
EBox::Module::Service::restartService('EBox::Samba=HASH(0x5591da249d60)', '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('samba', 'restartService', 'restart') called at /usr/share/perl5/EBox/Util/Init.pm line 247
EBox::Util::Init::moduleRestart('samba') called at /usr/bin/zs line 62
main::main at /usr/bin/zs line 82
2021/04/23 10:10:55 INFO> SyncDaemon.pm:340 EBox::Samba::SyncDaemon::run - Samba sync daemon started
le agradesco su ayuda
Rafael
zentyal 7.0.3
tengo el siguiente error al restart el modulo samba .he buscado en el forum y no he podido solucionar el problema
* Restarting Zentyal module: samba [fail]
root@zentyalplc:/# tail -f /var/log/zentyal/zentyal.log
2021/04/23 10:10:53 ERROR> Service.pm:969 EBox::Module::Service::restartService - Error restarting service: Could not get ticket: could not acquire credentials using an initial credentials context: Preauthentication failed
2021/04/23 10:10:53 ERROR> Service.pm:971 EBox::Module::Service::restartService - Could not get ticket: could not acquire credentials using an initial credentials context: Preauthentication failed
at Could not get ticket: could not acquire credentials using an initial credentials context: Preauthentication failed
at /usr/share/perl5/EBox/Module/Service.pm line 971
EBox::Module::Service::restartService('EBox::Samba=HASH(0x5591da249d60)', '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('samba', 'restartService', 'restart') called at /usr/share/perl5/EBox/Util/Init.pm line 247
EBox::Util::Init::moduleRestart('samba') called at /usr/bin/zs line 62
main::main at /usr/bin/zs line 82
2021/04/23 10:10:55 INFO> SyncDaemon.pm:340 EBox::Samba::SyncDaemon::run - Samba sync daemon started
le agradesco su ayuda
Rafael
4
Installation and Upgrades / Re: error mail upgrade 6 to 7 version
« on: March 29, 2021, 09:00:17 pm »
Hi
thanks for your quick response
samba-tool user list | grep 'zentyal-mail-'
The USER Zentyal-Mail-Zentyalplc P does not exist as it should occur and the ZS mail can not generate
As you could recreate user manually, by Jxplorer and samba-tool try to generate it and it tells me that I do not have permissions to create.
Try reinstalling the Mail module and generated me the same error mentioned above.
Best regards, havacuban
thanks for your quick response
samba-tool user list | grep 'zentyal-mail-'
The USER Zentyal-Mail-Zentyalplc P does not exist as it should occur and the ZS mail can not generate
As you could recreate user manually, by Jxplorer and samba-tool try to generate it and it tells me that I do not have permissions to create.
Try reinstalling the Mail module and generated me the same error mentioned above.
Best regards, havacuban
5
Installation and Upgrades / (SOLVED) error mail upgrade 6 to 7 version
« on: March 29, 2021, 05:17:37 pm »
Hi
I have problems with the Mail to Restart Module Service gives me the following error after upgrade 6 to 7
zentyal 7.0.3
module mail 7.0.1
zentyal pdc
error * Restarting Zentyal module: mail [fail]
Error en la creaci�n de entrada de LDAP: The request contains a value which does not meet with certain constraints.
This result can be returned as a consequence of
* The request was to add or modify a user password, and the password fails to
meet the criteria the server is configured to check. This could be that the
password is too short, or a recognizable word (e.g. it matches one of the
attributes in the users entry) or it matches a previous password used by
the same user.
* The request is a bind request to a user account that has been locked
.<br/> Operation parameters:'add []
'
Best regards, havacuban
-----------------SOLVED--------------------------
The issue was the rIDNextRID in samba update.
just modified that value whit
ldbedit -H /var/lib/samba/private/sam.ldb CN="RID Set"
and restart samba-ad-dc service
I have problems with the Mail to Restart Module Service gives me the following error after upgrade 6 to 7
zentyal 7.0.3
module mail 7.0.1
zentyal pdc
error * Restarting Zentyal module: mail [fail]
Error en la creaci�n de entrada de LDAP: The request contains a value which does not meet with certain constraints.
This result can be returned as a consequence of
* The request was to add or modify a user password, and the password fails to
meet the criteria the server is configured to check. This could be that the
password is too short, or a recognizable word (e.g. it matches one of the
attributes in the users entry) or it matches a previous password used by
the same user.
* The request is a bind request to a user account that has been locked
.<br/> Operation parameters:'add []
'
Best regards, havacuban
-----------------SOLVED--------------------------
The issue was the rIDNextRID in samba update.
just modified that value whit
ldbedit -H /var/lib/samba/private/sam.ldb CN="RID Set"
and restart samba-ad-dc service
6
Installation and Upgrades / Re: error proxy upgrade 6.2 to 7
« on: March 29, 2021, 05:10:16 pm »
Hi
Resolved the problem :
Jxplorer to the LDAP tree and delete the user Zentyal-Squid-ZentyalPLCB.
restart the squid
module squid status ok
Resolved the problem :
Jxplorer to the LDAP tree and delete the user Zentyal-Squid-ZentyalPLCB.
restart the squid
module squid status ok
7
Installation and Upgrades / Re: error proxy upgrade 6.2 to 7
« on: March 29, 2021, 04:14:27 pm »
Hi,
These are the outputs
zentyalplcb
dns-ZENTYALPLCB
Best regards, havacuban
These are the outputs
zentyalplcb
dns-ZENTYALPLCB
Best regards, havacuban
8
Installation and Upgrades / error proxy upgrade 6.2 to 7
« on: March 26, 2021, 11:06:25 pm »Hello
I have the following error in the log output
zentyal 7.0.3
HTTP Proxy 7.0.2
Additional Controller of an existing domain
* Restarting Zentyal module: squid [fail]
root command samba-tool group addmembers 'Domain Admins' zentyal-squid-zentyalplcb failed.
Error output: ldb_wrap open of secrets.ldb
string_to_sid: SID zentyal-squid-zentyalplcb is not in a valid format
ERROR(ldb): Failed to add members "zentyal-squid-zentyalplcb" to group "Domain Admins" - Attribute member already exists for target GUID e77c12ea-511e-4e12-977b-811024e77d75
File "/usr/lib/python3/dist-packages/samba/netcmd/group.py", line 245, in run
samdb.add_remove_group_members(groupname, groupmembers,
File "/usr/lib/python3/dist-packages/samba/samdb.py", line 320, in add_remove_group_members
self.modify_ldif(addtargettogroup)
File "/usr/lib/python3/dist-packages/samba/__init__.py", line 241, in modify_ldif
self.modify(msg, controls)
Command output: .
Exit value: 255
regards
9
Installation and Upgrades / Re: upgrade 6.2 to 7.0 - CA problem
« on: March 20, 2021, 06:04:09 pm »
Hello
I keep the problem
Zentyal-CA 7.0.1
Error desconocido. Se ofrece la salida de OpenSSL: Can't load /var/lib/zentyal/.rnd into RNG 140351545197888:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:98:Filename=/var/lib/zentyal/.rnd Generating a RSA private key ..................++++ .....................................................................++++ writing new private key to '/var/lib/zentyal/CA/private/cakey.pem' ----- Cannot write random bytes: 140351545197888:error:24070079:random number generator:RAND_write_file:Cannot open file:../crypto/rand/randfile.c:233:Filename=/var/lib/zentyal/.rnd
Solved the problem
remove zentyal-ca
delete .rd in / var / lib / zentyal
install zentyal-ca
I keep the problem
Zentyal-CA 7.0.1
Error desconocido. Se ofrece la salida de OpenSSL: Can't load /var/lib/zentyal/.rnd into RNG 140351545197888:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:98:Filename=/var/lib/zentyal/.rnd Generating a RSA private key ..................++++ .....................................................................++++ writing new private key to '/var/lib/zentyal/CA/private/cakey.pem' ----- Cannot write random bytes: 140351545197888:error:24070079:random number generator:RAND_write_file:Cannot open file:../crypto/rand/randfile.c:233:Filename=/var/lib/zentyal/.rnd
Solved the problem
remove zentyal-ca
delete .rd in / var / lib / zentyal
install zentyal-ca
10
Installation and Upgrades / Re: upgrade from 6.2 to 7.0
« on: February 17, 2021, 02:29:17 pm »
Hello
I have the same problem ?
havacuban
I have the same problem ?
havacuban
11
Spanish / Re: Error al realizar copia de seguridad
« on: April 20, 2020, 05:44:55 pm »
hola
Revisa el espacio de tu disco donde esta instalado el zentyal porque no puede hacer backup de seguridad por espacio,
por consola puedes usar este comando df -lh y observa el uso de las particiones que tienes en el disco.
saludos
Revisa el espacio de tu disco donde esta instalado el zentyal porque no puede hacer backup de seguridad por espacio,
por consola puedes usar este comando df -lh y observa el uso de las particiones que tienes en el disco.
saludos
12
Spanish / Re: Problemas con el dasboard
« on: December 19, 2019, 06:15:15 pm »
gracias por la pronta respuesta
bueno esto es lo que tengo
1. apt-get check
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
2.*** Starting uWSGI 2.0.15-debian (64bit) on [Tue Dec 17 10:43:06 2019] ***
compiled with version: 7.3.0 on 28 September 2018 15:41:15
os: Linux-4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019
nodename: correozentyal
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 8
current working directory: /
detected binary path: /usr/bin/uwsgi-core
dropping root privileges as early as possible
setgid() to 116
set additional group 4 (adm)
set additional group 42 (shadow)
setuid() to 110
your processes number limit is 31343
your memory page size is 4096 bytes
detected max file descriptor number: 1024
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address /run/zentyal-webadmin/webadmin.sock fd 3
dropping root privileges after socket binding
initialized Perl 5.26.1 main interpreter at 0x5578bb5d2eb0
dropping root privileges after plugin initialization
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 157824 bytes (154 KB) for 1 cores
*** Operational MODE: single process ***
PSGI app 0 (/usr/share/zentyal/psgi/zentyal.psgi) loaded in 0 seconds at 0x5578bfbc7340 (interpreter 0x5578bb5d2eb0)
dropping root privileges after application loading
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 9627)
spawned uWSGI worker 1 (pid: 9629, cores: 1)
Tue Dec 17 10:53:30 2019 - uwsgi_response_writev_headers_and_body_do(): Broken pipe [core/writer.c line 296] during GET / (127.0.0.1)
[pid: 9629|app: 0|req: 1/1] 127.0.0.1 () {46 vars in 710 bytes} [Tue Dec 17 10:43:06 2019] GET / => generated 0 bytes in 623722 msecs (HTTP/1.1 200) 2:
3.2019/10/14 09:46:33 [error] 4053#4053: *693291 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /SysInfo/RestartService?module=mail&restart=Reiniciar HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock", host: "localhost:8443", referrer: "https://localhost:8443/"
2019/10/14 09:46:53 [error] 4053#4053: *693232 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /Dashboard/WidgetJSON?module=sysinfo&widget=general HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock", host: "localhost:8443", referrer: "https://localhost:8443/Dashboard/Index"
2019/10/14 09:46:53 [error] 4053#4053: *693474 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /Dashboard/WidgetJSON?module=sysinfo&widget=modules HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock", host: "localhost:8443", referrer: "https://localhost:8443/Dashboard/Index"
2019/10/14 09:46:53 [error] 4053#4053: *693493 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /Dashboard/WidgetJSON?module=sysinfo&widget=links HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock", host: "localhost:8443", referrer: "https://localhost:8443/Dashboard/Index"
2019/10/14 09:46:53 [error] 4053#4053: *693483 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /Dashboard/WidgetJSON?module=network&widget=interfaces HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock", host: "localhost:8443", referrer: "https://localhost:8443/Dashboard/Index"
2019/10/14 09:46:53 [error] 4053#4053: *693669 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /Dashboard/WidgetJSON?module=dhcp&widget=dhcpleases HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock", host: "localhost:8443", referrer: "https://localhost:8443/Dashboard/Index"
2019/10/14 10:03:17 [error] 4053#4053: *693669 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /SysInfo/RestartService?module=mailfilter&restart=Reiniciar HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock", host: "localhost:8443", referrer: "https://localhost:8443/Dashboard/Index"
2019/11/25 14:42:53 [error] 4031#4031: *684 upstream prematurely closed connection while reading response header from upstream, client: 127.0.0.1, server: , request: "POST /SysInfo/Controller/Halt HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock:", host: "localhost:8443", referrer: "https://localhost:8443/SysInfo/View/Halt"
4.Zentyal: status module network: [ RUNNING ]
esto son las salidas de los log
saludos y gracias
bueno esto es lo que tengo
1. apt-get check
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
2.*** Starting uWSGI 2.0.15-debian (64bit) on [Tue Dec 17 10:43:06 2019] ***
compiled with version: 7.3.0 on 28 September 2018 15:41:15
os: Linux-4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019
nodename: correozentyal
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 8
current working directory: /
detected binary path: /usr/bin/uwsgi-core
dropping root privileges as early as possible
setgid() to 116
set additional group 4 (adm)
set additional group 42 (shadow)
setuid() to 110
your processes number limit is 31343
your memory page size is 4096 bytes
detected max file descriptor number: 1024
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address /run/zentyal-webadmin/webadmin.sock fd 3
dropping root privileges after socket binding
initialized Perl 5.26.1 main interpreter at 0x5578bb5d2eb0
dropping root privileges after plugin initialization
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 157824 bytes (154 KB) for 1 cores
*** Operational MODE: single process ***
PSGI app 0 (/usr/share/zentyal/psgi/zentyal.psgi) loaded in 0 seconds at 0x5578bfbc7340 (interpreter 0x5578bb5d2eb0)
dropping root privileges after application loading
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 9627)
spawned uWSGI worker 1 (pid: 9629, cores: 1)
Tue Dec 17 10:53:30 2019 - uwsgi_response_writev_headers_and_body_do(): Broken pipe [core/writer.c line 296] during GET / (127.0.0.1)
[pid: 9629|app: 0|req: 1/1] 127.0.0.1 () {46 vars in 710 bytes} [Tue Dec 17 10:43:06 2019] GET / => generated 0 bytes in 623722 msecs (HTTP/1.1 200) 2:
3.2019/10/14 09:46:33 [error] 4053#4053: *693291 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /SysInfo/RestartService?module=mail&restart=Reiniciar HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock", host: "localhost:8443", referrer: "https://localhost:8443/"
2019/10/14 09:46:53 [error] 4053#4053: *693232 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /Dashboard/WidgetJSON?module=sysinfo&widget=general HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock", host: "localhost:8443", referrer: "https://localhost:8443/Dashboard/Index"
2019/10/14 09:46:53 [error] 4053#4053: *693474 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /Dashboard/WidgetJSON?module=sysinfo&widget=modules HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock", host: "localhost:8443", referrer: "https://localhost:8443/Dashboard/Index"
2019/10/14 09:46:53 [error] 4053#4053: *693493 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /Dashboard/WidgetJSON?module=sysinfo&widget=links HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock", host: "localhost:8443", referrer: "https://localhost:8443/Dashboard/Index"
2019/10/14 09:46:53 [error] 4053#4053: *693483 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /Dashboard/WidgetJSON?module=network&widget=interfaces HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock", host: "localhost:8443", referrer: "https://localhost:8443/Dashboard/Index"
2019/10/14 09:46:53 [error] 4053#4053: *693669 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /Dashboard/WidgetJSON?module=dhcp&widget=dhcpleases HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock", host: "localhost:8443", referrer: "https://localhost:8443/Dashboard/Index"
2019/10/14 10:03:17 [error] 4053#4053: *693669 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /SysInfo/RestartService?module=mailfilter&restart=Reiniciar HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock", host: "localhost:8443", referrer: "https://localhost:8443/Dashboard/Index"
2019/11/25 14:42:53 [error] 4031#4031: *684 upstream prematurely closed connection while reading response header from upstream, client: 127.0.0.1, server: , request: "POST /SysInfo/Controller/Halt HTTP/1.1", upstream: "uwsgi://unix:///run/zentyal-webadmin/webadmin.sock:", host: "localhost:8443", referrer: "https://localhost:8443/SysInfo/View/Halt"
4.Zentyal: status module network: [ RUNNING ]
esto son las salidas de los log
saludos y gracias
13
Spanish / Problemas con el dasboard
« on: December 18, 2019, 05:17:12 pm »
hola comunidad
Tengo un problema después de actulizar el zentyal-core 6.1.2 no puedo abrir mi dasboard , me da el siguiente error 504 gateway time-out
revisando he modificado algunos parámetros en nginx pero sin resultados .
alguien me pude dar alguna pista para buscar ?
saludos
Tengo un problema después de actulizar el zentyal-core 6.1.2 no puedo abrir mi dasboard , me da el siguiente error 504 gateway time-out
revisando he modificado algunos parámetros en nginx pero sin resultados .
alguien me pude dar alguna pista para buscar ?
saludos
14
Spanish / Re: error en update
« on: December 13, 2019, 07:51:08 pm »
hola
resuelto mi problema , use esta vía
baje el paquete de aquí http://packages.zentyal.org/zentyal/dists/6.1/main/binary-i386/Packages.gz y renombre a
packages.zentyal.org_zentyal_dists_6.1_main_binary-i386_Packages.gz
lo moví por el que estaba con problemas /var/lib/apt/lists/partial/packages.zentyal.org_zentyal_dists_6.1_main_binary-i386_Packages.gz.FAILED
apt update
y no dio error y actualizo correctamente
saludos
resuelto mi problema , use esta vía
baje el paquete de aquí http://packages.zentyal.org/zentyal/dists/6.1/main/binary-i386/Packages.gz y renombre a
packages.zentyal.org_zentyal_dists_6.1_main_binary-i386_Packages.gz
lo moví por el que estaba con problemas /var/lib/apt/lists/partial/packages.zentyal.org_zentyal_dists_6.1_main_binary-i386_Packages.gz.FAILED
apt update
y no dio error y actualizo correctamente
saludos
15
Spanish / Re: error en update
« on: December 13, 2019, 07:11:24 pm »
hola
Gracias doncamilo por reponder ,mantengo el mismo problema, no se que comando poner para arreglar , pero ya limpie cache del apt y sigue igual.
saludos
Gracias doncamilo por reponder ,mantengo el mismo problema, no se que comando poner para arreglar , pero ya limpie cache del apt y sigue igual.
saludos