Server down since few hours and not response

Hello guys…

After i updated to 19.1 and also updated OLS to last version, Powerdns stop working…
I tried a LOT things i found in forums, nothing happens.
I´ve sent a ticket under platform.cyberpanel.net and nobody answered me yet. I´ve tried to escalate it sharing in twitter and facebook and inviting a colegue by email, but i can´t escalate neither.

I UNDERSTAND the free version have “limited” support, but if EACH time we update the panel we have problems, this is something to think if we still using the panel and recomingin it to colegues. The panel looks very weak if always broke in any update.

It was working perfect until my updates ,(
I´m really dissapointed…

Briefly, i have my server down since many hours, with production sites and a facebook ad running, is a real shame!

I hope someone can help me…

Regards
Fabian

please provide the error and the status from
systemcl status pdns
systemcl restart pdns

systemctl status pdns
● pdns.service - PowerDNS Authoritative Server
Loaded: loaded (/usr/lib/systemd/system/pdns.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2019-10-18 07 :19:08 CEST; 54ms ago
Docs: man:pdns_server(1)
man:pdns_control(1)
https://doc.powerdns.com
Process: 11047 ExecStart=/usr/sbin/pdns_server --guardian=no --daemon=no --dis able-syslog --log-timestamp=no --write-pid=no (code=exited, status=99)
Main PID: 11047 (code=exited, status=99)

Oct 18 07:19:08 hotsname.domain.com systemd[1]: Failed to start PowerDNS…
Oct 18 07:19:08 hotsname.domain.com systemd[1]: Unit pdns.service entere…
Oct 18 07:19:08 hotsname.domain.com systemd[1]: pdns.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

systemctl restart pdns
Job for pdns.service failed because the control process exited with error code. See “systemctl status pdns.service” and “journalctl -xe” for details.

I´ve tried to re-upgrade with : python upgrade.py

I get:

python upgrade.py
/usr/lib/python2.7/site-packages/requests/init.py:91: RequestsDependencyWarning: urllib3 (1.25.6) or chardet (2. 2.1) doesn’t match a supported version!
RequestsDependencyWarning)
Loaded plugins: fastestmirror
No Match for argument: yum-plugin-priorities
No Packages marked for removal

[10.18.2019_05-22-14] #########################################################################

[10.18.2019_05-22-14] remove yum-plugin-priorities successful.

[10.18.2019_05-22-14] #########################################################################

Traceback (most recent call last):
File “upgrade.py”, line 1949, in
main()
File “upgrade.py”, line 1945, in main
Upgrade.upgrade()
File “upgrade.py”, line 1867, in upgrade
Version = version.objects.get(pk=1)
File “/usr/lib64/python2.7/site-packages/django/db/models/manager.py”, line 85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File “/usr/lib64/python2.7/site-packages/django/db/models/query.py”, line 373, in get
num = len(clone)
File “/usr/lib64/python2.7/site-packages/django/db/models/query.py”, line 232, in len
self._fetch_all()
File “/usr/lib64/python2.7/site-packages/django/db/models/query.py”, line 1102, in _fetch_all
self._result_cache = list(self._iterable_class(self))
File “/usr/lib64/python2.7/site-packages/django/db/models/query.py”, line 53, in iter
results = compiler.execute_sql(chunked_fetch=self.chunked_fetch)
File “/usr/lib64/python2.7/site-packages/django/db/models/sql/compiler.py”, line 863, in execute_sql
sql, params = self.as_sql()
File “/usr/lib64/python2.7/site-packages/django/db/models/sql/compiler.py”, line 420, in as_sql
where, w_params = self.compile(self.where) if self.where is not None else ("", [])
File “/usr/lib64/python2.7/site-packages/django/db/models/sql/compiler.py”, line 373, in compile
sql, params = node.as_sql(self, self.connection)
File “/usr/lib64/python2.7/site-packages/django/db/models/sql/where.py”, line 79, in as_sql
sql, params = compiler.compile(child)
File “/usr/lib64/python2.7/site-packages/django/db/models/sql/compiler.py”, line 373, in compile
sql, params = node.as_sql(self, self.connection)
File “/usr/lib64/python2.7/site-packages/django/db/models/lookups.py”, line 169, in as_sql
lhs_sql, params = self.process_lhs(compiler, connection)
File “/usr/lib64/python2.7/site-packages/django/db/models/lookups.py”, line 162, in process_lhs
db_type = self.lhs.output_field.db_type(connection=connection)
File “/usr/lib64/python2.7/site-packages/django/db/models/fields/init.py”, line 640, in db_type
return connection.data_types[self.get_internal_type()] % data
File “/usr/lib64/python2.7/site-packages/django/utils/functional.py”, line 35, in get
res = instance.dict[self.name] = self.func(instance)
File “/usr/lib64/python2.7/site-packages/django/db/backends/mysql/base.py”, line 174, in data_types
if self.features.supports_microsecond_precision:
File “/usr/lib64/python2.7/site-packages/django/utils/functional.py”, line 35, in get
res = instance.dict[self.name] = self.func(instance)
File “/usr/lib64/python2.7/site-packages/django/db/backends/mysql/features.py”, line 53, in supports_microsecond_p recision
return self.connection.mysql_version >= (5, 6, 4) and Database.version_info >= (1, 2, 5)
File “/usr/lib64/python2.7/site-packages/django/utils/functional.py”, line 35, in get
res = instance.dict[self.name] = self.func(instance)
File “/usr/lib64/python2.7/site-packages/django/db/backends/mysql/base.py”, line 385, in mysql_version
with self.temporary_connection() as cursor:
File “/usr/lib64/python2.7/contextlib.py”, line 17, in enter
return self.gen.next()
File “/usr/lib64/python2.7/site-packages/django/db/backends/base/base.py”, line 591, in temporary_connection
cursor = self.cursor()
File “/usr/lib64/python2.7/site-packages/django/db/backends/base/base.py”, line 254, in cursor
return self._cursor()
File “/usr/lib64/python2.7/site-packages/django/db/backends/base/base.py”, line 229, in _cursor
self.ensure_connection()
File “/usr/lib64/python2.7/site-packages/django/db/backends/base/base.py”, line 213, in ensure_connection
self.connect()
File “/usr/lib64/python2.7/site-packages/django/db/utils.py”, line 94, in exit
six.reraise(dj_exc_type, dj_exc_value, traceback)
File “/usr/lib64/python2.7/site-packages/django/db/backends/base/base.py”, line 213, in ensure_connection
self.connect()
File “/usr/lib64/python2.7/site-packages/django/db/backends/base/base.py”, line 189, in connect
self.connection = self.get_new_connection(conn_params)
File “/usr/lib64/python2.7/site-packages/django/db/backends/mysql/base.py”, line 274, in get_new_connection
conn = Database.connect(**conn_params)
File “/usr/lib64/python2.7/site-packages/MySQLdb/init.py”, line 81, in Connect
return Connection(*args, **kwargs)
File “/usr/lib64/python2.7/site-packages/MySQLdb/connections.py”, line 193, in init
super(Connection, self).init(*args, **kwargs2)
django.db.utils.OperationalError: (2003, 'Can\'t connect to MySQL server on \‘127.0.0.1\’ (111 “Connection refused”) ')

i see many times i had similar problems the cyberpanel support told me this:

" Your settings file was missing"
or
" We fixed your settings file"

But i never know how i can fix it ;(
I´m pretty sure that is the problem

Your settings file would be located here on the server
/usr/local/CyberCP/CyberCP/settings.py

You can download a fresh copy from the github if yours is broken. Make sure to backup the passwords for mysql from there though.
https://github.com/usmannasir/cyberpanel/blob/1.8.0/CyberCP/settings.py

raw
https://github.com/usmannasir/cyberpanel/raw/1.8.0/CyberCP/settings.py

You would want to make sure the cyberpanel user mysql password and the root password match in the settings file with what they are and start mysql

Mysql root Password should be in here and ideally be valid
cat /etc/cyberpanel/mysqlPassword

If the password is wrong this can bork everything and may require you resetting the root password and cyberpanel users mysql and updating the settings file and the mysql root password file.

Sometimes pdns can fail to start due to perms for pdns. try the below for your OS and see if that helps

CentOS Linux release 7.7.1908 (Core)
chown root:root /etc/pdns/pdns.conf
chmod 600 /etc/pdns/pdns.conf

=========================
You may want to open a ticket if still having trouble cause it does sound like something is seriously jacked up.

Also in regards to the url requests error you will want to try the below most likley.
pip install requests urllib3 pyOpenSSL --upgrade

Thanks for your help!

I do EVERYTHING… nothing changes
When i try to restart PDNS:

Job for pdns.service failed because the control process exited with error code. See “systemctl status pdns.service” and “journalctl -xe” for details.

I have all down since more of 30 hours, in support only asnwered me:

"Hello

Sorry for the late reply. I’ve managed to bring PDNS up, but your MySQL server is down.

Kindly bring up MySQL server (it is out of the scope of our free support). Once MySQL is up, CyberPanel will also start working."

mySQL is perfect, i can login as root, and is running fine.
I´ve already replied the ticket, but still waiting…

Is INCREDIBLE that we can´t upgrade cyberpanel without issues…
I love this panel, but this can´t happens, i need to find some other panel ;(