We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on Vesta 2.0 and expect to release it by the end of 2024. Read more about it: https://vestacp.com/docs/vesta-2-development
After Update Problems with DNS
Re: After Update Problems with DNS
- make backup your main.sh
- nano your main.sh and delete all inside
- copy new data from
https://raw.githubusercontent.com/Skama ... nc/main.sh to your empty main.sh
- nano your main.sh and delete all inside
- copy new data from
https://raw.githubusercontent.com/Skama ... nc/main.sh to your empty main.sh
Re: After Update Problems with DNS
Thank you! It helps!
Re: After Update Problems with DNS
hallo,
i have same problem (can't start named), and already try backup main.sh, add new main.sh from github and restart the vesta service, but still fail to start named service, any help ?
i have same problem (can't start named), and already try backup main.sh, add new main.sh from github and restart the vesta service, but still fail to start named service, any help ?
Code: Select all
● named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2016-11-25 08:29:34 WIB; 9s ago
Process: 13534 ExecStop=/bin/sh -c /usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID (code=exited, status=0/SUCCESS)
Process: 12995 ExecStart=/usr/sbin/named -u named $OPTIONS (code=exited, status=0/SUCCESS)
Process: 6298 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z /etc/named.conf; else echo "Checking of zone files is disabled"; fi (code=exited, status=1/FAILURE)
Main PID: 12997 (code=exited, status=0/SUCCESS)
Nov 25 08:29:34 co.XX.com bash[6298]: dns_rdata_fromtext: /home/admin/conf/dns/XXXXX.com.db:19: syntax error
[b]Nov 25 08:29:34 co.XX.com bash[6298]: zone XXXXX.com/IN: loading from master file /home/admin/conf/dns/XXXXX...x error[/b]
Nov 25 08:29:34 co.XX.com bash[6298]: zone XXXXX.com/IN: not loaded due to errors.
Nov 25 08:29:34 co.XX.com bash[6298]: _default/XXXXX.com/IN: syntax error
Nov 25 08:29:34 co.XX bash[6298]: zone tasmurah.id/IN: loaded serial 2016112520
Nov 25 08:29:34 co.XX.com bash[6298]: zone tes.XX.com/IN: loaded serial 2016112502
Nov 25 08:29:34 co.XX.com systemd[1]: named.service: control process exited, code=exited status=1
Nov 25 08:29:34 co.XX.com systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Nov 25 08:29:34 co.XX.com systemd[1]: Unit named.service entered failed state.
Nov 25 08:29:34 co.XX.com systemd[1]: named.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
Re: After Update Problems with DNS
azreal, try to rebuild dns for your domains.
Re: After Update Problems with DNS
I'm having the same issue. I have restored my main.sh and Rebuilt my only ADMIN user DNS.
Post update I'm still experiencing a slooooooownes when connecting via SSH and any admin functions in Magento CMS.
Anything else to try without firing up a new instance of VESTA and starting over?
Post update I'm still experiencing a slooooooownes when connecting via SSH and any admin functions in Magento CMS.
Anything else to try without firing up a new instance of VESTA and starting over?