Author Topic: [HELP] ZENTYAL 5.0 SERVER FILE SHARE PROBLEM  (Read 788 times)

jheyford

  • Zen Apprentice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
[HELP] ZENTYAL 5.0 SERVER FILE SHARE PROBLEM
« on: July 17, 2018, 05:54:18 am »
Hello guys,

Can anyone help me regarding this issue. the server was pinging but there's a time we cant access to server file sharing and we need to restart the zentyal to access again  :-[ its already 5 times happend.

Sorry for my bad english.

JLLEWELYN

  • Zen Monk
  • **
  • Posts: 58
  • Karma: +4/-0
    • View Profile
Re: [HELP] ZENTYAL 5.0 SERVER FILE SHARE PROBLEM
« Reply #1 on: July 17, 2018, 11:32:47 pm »
The same thing happened to me in version 5.0, after updating to version 5.1.1 it works well for me.

JLLEWELYN

  • Zen Monk
  • **
  • Posts: 58
  • Karma: +4/-0
    • View Profile
Re: [HELP] ZENTYAL 5.0 SERVER FILE SHARE PROBLEM
« Reply #2 on: July 26, 2018, 08:23:47 pm »
The same thing happened to me in version 5.0, after updating to version 5.1.1 it works well for me.

I had the same problem, stops authenticating users and stops sharing folders.

Code: [Select]
● bind9.service - BIND Domain Name Server
   Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
  Drop-In: /run/systemd/generator/bind9.service.d
           └─50-insserv.conf-$named.conf
   Active: failed (Result: exit-code) since jue 2018-07-26 13:18:58 -04; 52min ago
     Docs: man:named(8)
 Main PID: 3141 (code=killed, signal=ABRT)

jul 26 13:18:36 servidor named[3141]: automatic empty zone: EMPTY.AS112.ARPA
jul 26 13:18:38 servidor named[3141]: configuring command channel from '/etc/bind/rndc.key
jul 26 13:18:38 servidor named[3141]: reloading configuration succeeded
jul 26 13:18:38 servidor named[3141]: any newly configured zones are now loaded
jul 26 13:18:39 servidor named[3141]: success resolving 'star-z-mini.c10r.facebook.com/A'
jul 26 13:18:58 servidor systemd[1]: bind9.service: Main process exited, code=killed, stat
jul 26 13:18:58 servidor rndc[30141]: rndc: connect failed: 127.0.0.1#953: connection refu
jul 26 13:18:58 servidor systemd[1]: bind9.service: Control process exited, code=exited st
jul 26 13:18:58 servidor systemd[1]: bind9.service: Unit entered failed state.
jul 26 13:18:58 servidor systemd[1]: bind9.service: Failed with result 'exit-code'.

the solution:
Code: [Select]
administrator@servidor:~$ sudo systemctl restart bind9
administrator@servidor:~$ sudo systemctl status bind9
● bind9.service - BIND Domain Name Server
   Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
  Drop-In: /run/systemd/generator/bind9.service.d
           └─50-insserv.conf-$named.conf
   Active: active (running) since jue 2018-07-26 14:13:35 -04; 2s ago
     Docs: man:named(8)
 Main PID: 12404 (named)
    Tasks: 7
   Memory: 49.7M
      CPU: 217ms
   CGroup: /system.slice/bind9.service
           └─12404 /usr/sbin/named -f -u bind -4

jul 26 14:13:36 servidor named[12404]: zone 168.192.in-addr.arpa/IN: loaded serial 1
jul 26 14:13:36 servidor named[12404]: zone 24.172.in-addr.arpa/IN: loaded serial 1
jul 26 14:13:36 servidor named[12404]: zone 23.172.in-addr.arpa/IN: loaded serial 1
jul 26 14:13:36 servidor named[12404]: zone 127.in-addr.arpa/IN: loaded serial 1
jul 26 14:13:36 servidor named[12404]: zone 27.172.in-addr.arpa/IN: loaded serial 1
jul 26 14:13:36 servidor named[12404]: zone 16.172.in-addr.arpa/IN: loaded serial 1
jul 26 14:13:36 servidor named[12404]: zone 28.172.in-addr.arpa/IN: loaded serial 1
jul 26 14:13:36 servidor named[12404]: zone 1.168.192.in-addr.arpa/IN: loaded serial 20180
jul 26 14:13:36 servidor named[12404]: all zones loaded
jul 26 14:13:36 servidor named[12404]: running
lines 1-23