Recent Posts

1

Russian / Re: Zentyal 7.0 и статический адрес провайдера

« Last post by luha on Today at 02:07:05 pm »

Нужно проверить настройки DHCP сервера, а точнее какой там указан сервер DNS. На компьютере пользователя посмотреть свойства подключения на тот же предмет поиска.

2

Russian / Re: Zentyal 7.0 и статический адрес провайдера

« Last post by IIS on Today at 01:57:37 pm »

Понятно что к DNS.
У меня в работе 5я версия там все работает. в 7й настроил по аналогии и не работает

3

Russian / Re: Zentyal 7.0 и статический адрес провайдера

« Last post by luha on Today at 09:09:04 am »

Если по имени не пингуется а по ip пингуется то это к DNS.

4

Russian / Zentyal 7.0 и статический адрес провайдера

« Last post by IIS on March 21, 2023, 09:05:36 pm »

Приветствую
Объясните как правильно настроить сервер в качестве интернет шлюза.
провайдер смотрит со стороны eth2 ip статический 17.22.22.10
eth1 смотрит в локалку на нем адрес 192.168.1.1 настроен dhcp  клиенты ip получают сервер видят
но инета нет, по имени не пингуются внешние ресурсы.(ya.ru) а по ip пингуются.
На самом сервере ситуация аналогичная.

5

Installation and Upgrades / Zentyal Server stopped working

« Last post by Faisal Abbas on March 20, 2023, 02:12:48 pm »

Dear Support Team,

My Zentyal Server is not working, i have followed your previous link and change stderr to stdout  in Ldap.pm file, then after restart i am getting below error in zentyal.log file

2023/03/20 18:05:58 INFO> SyncDaemon.pm:340 EBox::Samba::SyncDaemon::run - Samba sync daemon started
2023/03/20 18:05:59 ERROR> Ldap.pm:257 EBox::Ldap::dn - Error loading LDIF. Error message: First line tered
GENSEC backend 'gssapi_krb5' registered
GENSEC backend 'gssapi_krb5_sasl' registered
GENSEC backend 'spnego' registered
GENSEC backend 'schannel' registered
GENSEC backend 'naclrpc_as_system' registered
GENSEC backend 'sasl-EXTERNAL' registered
GENSEC backend 'ntlmssp' registered
GENSEC backend 'ntlmssp_resume_ccache' registered
GENSEC backend 'http_basic' registered
GENSEC backend 'http_ntlm' registered
GENSEC backend 'http_negotiate' registered
GENSEC backend 'krb5' registered
GENSEC backend 'fake_gssapi_krb5' registered
dn: DC=sapphirecs,DC=net at Error loading LDIF. Error message: First line of LDIF entry does not begin
GENSEC backend 'gssapi_krb5' registered
GENSEC backend 'gssapi_krb5_sasl' registered
GENSEC backend 'spnego' registered
GENSEC backend 'schannel' registered
GENSEC backend 'naclrpc_as_system' registered
GENSEC backend 'sasl-EXTERNAL' registered
GENSEC backend 'ntlmssp' registered
GENSEC backend 'ntlmssp_resume_ccache' registered
GENSEC backend 'http_basic' registered
GENSEC backend 'http_ntlm' registered
GENSEC backend 'http_negotiate' registered
GENSEC backend 'krb5' registered
GENSEC backend 'fake_gssapi_krb5' registered
dn: DC=sapphirecs,DC=net at /usr/share/perl5/EBox/Ldap.pm line 257
EBox::Ldap::dn('EBox::Ldap=HASH(0x562f45578010)') called at /usr/share/perl5/EBox/Ldap.pm line 293
EBox::Ldap::domainSID('EBox::Ldap=HASH(0x562f45578010)') called at /usr/share/perl5/EBox/Samba/SyncDae
EBox::Samba::SyncDaemon::setACLs('EBox::Samba::SyncDaemon=HASH(0x562f455a71d8)') called at /usr/share/
EBox::Samba::SyncDaemon::run('EBox::Samba::SyncDaemon=HASH(0x562f455a71d8)', 30, 10) called at /usr/sh
2023/03/20 18:06:04 INFO> SyncDaemon.pm:340 EBox::Samba::SyncDaemon::run - Samba sync daemon started
^C




Kindy Help.

6

Installation and Upgrades / Re: ZENTYAL CONFIGURATION BACKUP ERROR

« Last post by turalyon on March 20, 2023, 12:28:36 pm »

That bug was reported and fixed last week. You must update the domain controller package to 'zentyal-samba-7.0.2'. In case you do not have that update available is because you do not have access to the Zentyal repository. You can confirm it by running the following command:

Code: [Select]

sudo apt update

If this is the case, below you have a link where the required actions are explained:

* https://forum.zentyal.org/index.php/topic,35100.msg115467.html#msg115467

--

“This world is ours, and by the Holy Light we will keep it safe, now and forever".

7

Russian / Re: Element not found

« Last post by AntonMosyagin on March 20, 2023, 10:50:44 am »

У вас проблемы с  nginx

Code: [Select]

мар 20 10:04:13 zentyaladmin nginx[49953]: nginx: [emerg] still could not bind()
мар 20 10:04:13 zentyaladmin systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
мар 20 10:04:13 zentyaladmin systemd[1]: nginx.service: Failed with result 'exit-code'.
мар 20 10:04:13 zentyaladmin systemd[1]: Failed to start A high performance web server and a reverse proxy server.

Есть варианты решения проблемы?

Решил проблему обновлением nginx. Благодарю за наводку!!!

8

Russian / Re: Element not found

« Last post by AntonMosyagin on March 20, 2023, 10:00:50 am »

У вас проблемы с  nginx

Code: [Select]

мар 20 10:04:13 zentyaladmin nginx[49953]: nginx: [emerg] still could not bind()
мар 20 10:04:13 zentyaladmin systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
мар 20 10:04:13 zentyaladmin systemd[1]: nginx.service: Failed with result 'exit-code'.
мар 20 10:04:13 zentyaladmin systemd[1]: Failed to start A high performance web server and a reverse proxy server.

Есть варианты решения проблемы?

9

Russian / Re: Element not found

« Last post by tunsa on March 20, 2023, 09:33:23 am »

У вас проблемы с  nginx

Code: [Select]

мар 20 10:04:13 zentyaladmin nginx[49953]: nginx: [emerg] still could not bind()
мар 20 10:04:13 zentyaladmin systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
мар 20 10:04:13 zentyaladmin systemd[1]: nginx.service: Failed with result 'exit-code'.
мар 20 10:04:13 zentyaladmin systemd[1]: Failed to start A high performance web server and a reverse proxy server.

10

Russian / Re: Element not found

« Last post by AntonMosyagin on March 20, 2023, 08:11:14 am »

Пробовали рестартануть nginx ?

Code: [Select]

service nginx restartservice nginx restart
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xe" for details.

А лучше проверить для начала все ли ок со службой.

Code: [Select]

service nginx status
nginx.service - A high performance web server and a reverse proxy server
     Loaded: loaded (/lib/systemd/system/nginx.service; disabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Mon 2023-03-20 10:04:13 MSK; 2min 6s ago
       Docs: man:nginx(
    Process: 49952 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
    Process: 49953 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=1/FAILURE)

мар 20 10:04:10 zentyaladmin systemd[1]: Starting A high performance web server and a reverse proxy server...
мар 20 10:04:10 zentyaladmin nginx[49953]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
мар 20 10:04:11 zentyaladmin nginx[49953]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
мар 20 10:04:11 zentyaladmin nginx[49953]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
мар 20 10:04:12 zentyaladmin nginx[49953]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
мар 20 10:04:12 zentyaladmin nginx[49953]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
мар 20 10:04:13 zentyaladmin nginx[49953]: nginx: [emerg] still could not bind()
мар 20 10:04:13 zentyaladmin systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
мар 20 10:04:13 zentyaladmin systemd[1]: nginx.service: Failed with result 'exit-code'.
мар 20 10:04:13 zentyaladmin systemd[1]: Failed to start A high performance web server and a reverse proxy server.

Места на диске достаточно?

Code: [Select]

df -hFilesystem      Size  Used Avail Use% Mounted on
udev            1,9G     0  1,9G   0% /dev
tmpfs           393M  3,2M  390M   1% /run
/dev/sda5       916G   12G  857G   2% /
tmpfs           2,0G  4,0K  2,0G   1% /dev/shm
tmpfs           5,0M     0  5,0M   0% /run/lock
tmpfs           2,0G     0  2,0G   0% /sys/fs/cgroup
/dev/sda1       511M  4,0K  511M   1% /boot/efi
tmpfs           393M  4,0K  393M   1% /run/user/1000

Что в логах?

Code: [Select]

journalctl -xe--
-- The unit zentyal.samba-sync.service has entered the 'failed' state with result 'exit-code'.
мар 20 10:10:46 zentyaladmin systemd[1]: zentyal.samba-sync.service: Scheduled restart job, restart counter is at 2316.
-- Subject: Назначен автоматический перезапуск юнита
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Назначен автоматический перезапуск юнита zentyal.samba-sync.service, так как для него был задан
-- параметр Restart=.
мар 20 10:10:46 zentyaladmin systemd[1]: Stopped Zentyal daemon to check uid and gid numbers.
-- Subject: Завершена остановка юнита zentyal.samba-sync.service.
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Процесс остановки юнита zentyal.samba-sync.service был завершен.
мар 20 10:10:46 zentyaladmin systemd[1]: Started Zentyal daemon to check uid and gid numbers.
-- Subject: Запуск юнита zentyal.samba-sync.service завершен
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Процесс запуска юнита zentyal.samba-sync.service был завершен.
--
-- Результат: done.