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.


Messages - fvnet

Pages: [1]
1
P.S in my case i removed the

MariaDB-backup-10.11.13-1.el8.x86_64
mariadb-gssapi-server-10.3.39-1.module_el8.8.0+3609+204d4ab0.x86_64
MariaDB-devel-10.11.13-1.el8.x86_64

They were not re-installed but I am not sure if they were needed.
Could someone advise whether they were actually needed or not??

2
OK, i re-did the whole manual upgrade.
For any friends wanting to do the same here are the steps for Alma Linux 8(based on the https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-8-stream-almalinux-78-rockylinux-78/ )

First, backup your current my.cnf config :

cp /etc/my.cnf /etc/my.cnf.bak

Remove MariaDB 10.0/10.1/10.2/10.3/10.xx :

Code: [Select]
systemctl stop mariadb mysql mysqld
systemctl disable mariadb
rpm --nodeps -ev MariaDB-server

then run the following to view remaining mariadb instalaltions

Code: [Select]
rpm -qa|grep -i maria
remove the remaining by using rpm --nodeps -ev
for example
Code: [Select]
rpm --nodeps -ev MariaDB-client
follow the above external forum link to install the latest mariadb

in the end i had these

 
Code: [Select]
rpm -qa|grep -i maria
MariaDB-common-10.11.13-1.el8.x86_64
MariaDB-client-10.11.13-1.el8.x86_64
MariaDB-server-10.11.13-1.el8.x86_64
MariaDB-shared-10.11.13-1.el8.x86_64




3
hmm, you are right, the server part was not updated

Any quck way to update that only? Or do I go again using the usual process?
Code: [Select]
rpm -qa|grep -i maria
MariaDB-server-10.11.11-1.el8.x86_64
MariaDB-backup-10.11.13-1.el8.x86_64
mariadb-gssapi-server-10.3.39-1.module_el8.8.0+3609+204d4ab0.x86_64
MariaDB-shared-10.11.13-1.el8.x86_64
MariaDB-devel-10.11.13-1.el8.x86_64
MariaDB-client-10.11.13-1.el8.x86_64
MariaDB-common-10.11.13-1.el8.x86_64


4
Hello dear friends.
I also re-installed my Hetzner server using AL8 and the CWOP Pro and everything works OK. I also did the upgrade to MariaDB 10.11 using this as help (it needs attention though, not that straightforward but anyway)
https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-8-stream-almalinux-78-rockylinux-78/

Now the dashboard states: MySQL version: 10.11.13-MariaDB
The YUM offers me to upgrade to 10.11.13-1.el8 which fails
Honestly i don't mind not upgrading, but it bothers me that when there are other updates the Update All button doesn't work due to MariaDB. Any way to overcome this??

Code: [Select]
Last metadata expiration check: 2:29:12 ago on Mon May 26 07:12:20 2025.
Dependencies resolved.
================================================================================
 Package               Architecture  Version               Repository      Size
================================================================================
Upgrading:
 MariaDB-server        x86_64        10.11.13-1.el8        mariadb         28 M

Transaction Summary
================================================================================
Upgrade  1 Package

Total size: 28 M
Downloading Packages:
[SKIPPED] MariaDB-server-10.11.13-1.el8.x86_64.rpm: Already downloaded         
Running transaction check
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'yum clean packages'.

5
Hello dear friends,
I run my server flawlessly with CWP Pro with 547 days uptime. Perfect.

Could you help me out a little with this annoying emailing every day (I think it started a month ago or so)

Code: [Select]
Cron <root@d1> /usr/local/cwp/php71/bin/php /usr/local/cwpsrv/htdocs/resources/admin/include/cron_autossl_all_domains.php
CREATION FAILEDS: 0
CREATEDS: 0
RENEWAL FAILEDS: 0
RENEWEDS: 0

I shouldn't receive these as I have NOT ticked that "email autorenewal..", right?

https://www.dropbox.com/s/doo2uudfddyqib4/sc01_161659.jpg?dl=0


6
Can I ask please a simple question?
Running CWPpro version: 0.9.8.721 on Centos7
I have enabled the protection (as shown in the screenshot link below) but noticed that after reboot it comes up again as Disabled Temporarily.
Is it normal?

https://www.dropbox.com/s/uh11yv2thhp95az/cwpsc1.jpg?dl=0

Thanks in advance

7
CentOS 7 Problems / Re: CWP Pro: Server reboot occurrence
« on: September 06, 2018, 06:42:53 PM »
And by the way, it's the second time this has occurred.
You can check status here
https://www.hetzner-status.de/en.html
If you want to know your cloud node ID just tracert your servers IP.

8
CentOS 7 Problems / Re: CWP Pro: Server reboot occurrence
« on: September 05, 2018, 03:47:05 PM »
Hello again, I will answer it myself.
The provider (Hetzner) actually rebooted the hostnode due to a problem.

9
CentOS 7 Problems / CWP Pro: Server reboot occurrence
« on: September 01, 2018, 06:48:35 PM »
Hello dear friends,
I am running CWP Pro on a Hetzner cloud and every now and then I login to check for any issues. In yesterday's login I saw that the server uptime is 1 day and some hours which puzzled me as the VM is running for almost 20 days without reboot.

In var\log\messages I spotted this

Code: [Select]
Aug 30 09:28:53 d1 qemu-ga: info: guest-shutdown called, mode: powerdown
Aug 30 09:28:53 d1 systemd: Started Delayed Shutdown Service.
Aug 30 09:28:53 d1 systemd: Starting Delayed Shutdown Service...
Aug 30 09:28:53 d1 systemd-shutdownd: Shutting down at Thu 2018-08-30 09:28:53 CEST (poweroff)...
Aug 30 09:28:53 d1 systemd-shutdownd: Creating /run/nologin, blocking further logins...
Aug 30 09:28:53 d1 systemd: Stopped Dump dmesg to /var/log/dmesg.
Aug 30 09:28:53 d1 systemd: Stopping Dump dmesg to /var/log/dmesg...
Aug 30 09:28:53 d1 systemd: Stopping clamd scanner () daemon...
Aug 30 09:28:53 d1 systemd: Stopped target Timers.
Aug 30 09:28:53 d1 systemd: Stopping Timers.
Aug 30 09:28:53 d1 systemd: Stopped Daily Cleanup of Temporary Directories.
Aug 30 09:28:53 d1 systemd: Stopping Daily Cleanup of Temporary Directories.
Aug 30 09:28:53 d1 systemd: Stopped Amavisd clean tmp timer.
Aug 30 09:28:53 d1 systemd: Stopping Amavisd clean tmp timer.
Aug 30 09:28:53 d1 systemd: Stopped Amavisd clean quarantine timer.
Aug 30 09:28:53 d1 systemd: Stopping Amavisd clean quarantine timer.
Aug 30 09:28:53 d1 systemd: Stopping Authorization Manager...
Aug 30 09:28:53 d1 systemd: Stopping QEMU Guest Agent...
Aug 30 09:28:53 d1 systemd: Stopping Session 3189 of user root.
Aug 30 09:39:33 d1 kernel: Initializing cgroup subsys cpuset
Aug 30 09:39:33 d1 kernel: Initializing cgroup subsys cpu
Aug 30 09:39:33 d1 kernel: Initializing cgroup subsys cpuacct
Aug 30 09:39:33 d1 kernel: Linux version 3.10.0-862.9.1.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC) ) #1 SMP Mon Jul 16 16:29:36 UTC 2018
Aug 30 09:39:33 d1 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-3.10.0-862.9.1.el7.x86_64
I am attaching the screenshots and I am wondering is something that has to do with CWP or do I have to contact the provider?

https://www.dropbox.com/s/kavjhsiqtazlkvo/sc1.jpg?dl=0
https://www.dropbox.com/s/u26u0myc7mm0h2n/sc2.jpg?dl=0



Pages: [1]