Need help with DA license

MRP

New member
Joined
Aug 5, 2021
Messages
3
Hey Everyone.

I have a question and also an interesting problem. My server has an expired trial license for about a year now. I didn't need to use da for that long as everything was working good. Now mysql is down and even rebooting doesn't help. I can't login to SSH I think the firewall is blocking my IP which changes often. When I go to DA login on my server it says: "Hmm, login details do not seem to be correct. Please try again" I know the license was trial and it expired. The question here is if I buy a full license will it update automatiacally and let me in so I can fix the server? Keep in mind I'm blocked from accessing SSH due to IP I think.
 
Hey Everyone.

I have a question and also an interesting problem. My server has an expired trial license for about a year now. I didn't need to use da for that long as everything was working good. Now mysql is down and even rebooting doesn't help. I can't login to SSH I think the firewall is blocking my IP which changes often. When I go to DA login on my server it says: "Hmm, login details do not seem to be correct. Please try again" I know the license was trial and it expired. The question here is if I buy a full license will it update automatiacally and let me in so I can fix the server? Keep in mind I'm blocked from accessing SSH due to IP I think.
Yes and no.
Its exactly that, a new license.
So the license file need to be updated as you will receive a new key.
This needs to happen with SSH access or an other direct way to access the server.
The key is also automatically added by the DirectAdmin installer. (But since you already have an install, this would require a server wipe.)
 
yes, buy and update a new license. Then update all the packages. hope it will solve
 
Thanks for your help. I was able to get into ssh.

But don't know how to fix mysql ;(

Failed to start MySQL Server.
Unit mysqld.service entered failed state.
mysqld.service failed.
mysqld.service holdoff time over, scheduling restart.
Stopped MySQL Server.
start request repeated too quickly for mysqld.service
Failed to start MySQL Server.
Unit mysqld.service entered failed state.
mysqld.service failed.

any ideas how to fix this probem>

systemctl status mysqld
● mysqld.service - MySQL Server
Loaded: loaded (/etc/systemd/system/mysqld.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Thu 2021-08-05 14:31:10 CDT; 31s ago
Docs: man:mysqld(8)
http://dev.mysql.com/doc/refman/en/using-systemd.html
Process: 9911 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid $MYSQLD_OPTS (code=exited, status=1/FAILURE)
Process: 9887 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)


I found more errors I might be out of space or soemthing how to check that?

[Note] InnoDB: Starting crash recovery.
[Note] InnoDB: Creating shared tablespace for temporary tables
[Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
[Warning] InnoDB: Retry attempts for writing partial data failed.
[ERROR] InnoDB: Write to file ./ibtmp1failed at offset 0, 1048576 bytes should have been written, only 0 were written. Ope...
[ERROR] InnoDB: Error number 28 means 'No space left on device'
[Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/op...or-codes.html
[ERROR] InnoDB: Could not set the file size of './ibtmp1'. Probably out of disk space
[ERROR] InnoDB: Unable to create the shared innodb_temporary
[ERROR] InnoDB: Plugin initialization aborted with error Generic error
 
Last edited:
Thanks for your help. I was able to get into ssh.

But don't know how to fix mysql ;(

Failed to start MySQL Server.
Unit mysqld.service entered failed state.
mysqld.service failed.
mysqld.service holdoff time over, scheduling restart.
Stopped MySQL Server.
start request repeated too quickly for mysqld.service
Failed to start MySQL Server.
Unit mysqld.service entered failed state.
mysqld.service failed.

any ideas how to fix this probem>

systemctl status mysqld
● mysqld.service - MySQL Server
Loaded: loaded (/etc/systemd/system/mysqld.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Thu 2021-08-05 14:31:10 CDT; 31s ago
Docs: man:mysqld(8)
http://dev.mysql.com/doc/refman/en/using-systemd.html
Process: 9911 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid $MYSQLD_OPTS (code=exited, status=1/FAILURE)
Process: 9887 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)


I found more errors I might be out of space or soemthing how to check that?

[Note] InnoDB: Starting crash recovery.
[Note] InnoDB: Creating shared tablespace for temporary tables
[Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
[Warning] InnoDB: Retry attempts for writing partial data failed.
[ERROR] InnoDB: Write to file ./ibtmp1failed at offset 0, 1048576 bytes should have been written, only 0 were written. Ope...
[ERROR] InnoDB: Error number 28 means 'No space left on device'
[Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/op...or-codes.html
[ERROR] InnoDB: Could not set the file size of './ibtmp1'. Probably out of disk space
[ERROR] InnoDB: Unable to create the shared innodb_temporary
[ERROR] InnoDB: Plugin initialization aborted with error Generic error
Do you have any diskspace left? It's telling it cannot write data to disk because of no space.
 
Do you have any diskspace left? It's telling it cannot write data to disk because of no space.
here is what it shows

df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.6G 0 7.6G 0% /dev
tmpfs 7.7G 0 7.7G 0% /dev/shm
tmpfs 7.7G 145M 7.5G 2% /run
tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup
/dev/mapper/vg-root 101G 96G 0 100% /
/dev/sda2 1008M 171M 787M 18% /boot
/dev/sdb1 1.8T 523G 1.2T 31% /home
/dev/mapper/vg-tmp 976M 2.8M 906M 1% /tmp
tmpfs 1.6G 0 1.6G 0% /run/user/0
tmpfs 1.6G 0 1.6G 0% /run/user/1009

One shows 100% used /dev/mapper/vg-root 101G 96G 0 100% /
could this be the problem? if so how to fix this? how do I know where file is trying to be written?
Could not set the file size of './ibtmp1'. Probably out of disk space
 
here is what it shows

df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.6G 0 7.6G 0% /dev
tmpfs 7.7G 0 7.7G 0% /dev/shm
tmpfs 7.7G 145M 7.5G 2% /run
tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup
/dev/mapper/vg-root 101G 96G 0 100% /
/dev/sda2 1008M 171M 787M 18% /boot
/dev/sdb1 1.8T 523G 1.2T 31% /home
/dev/mapper/vg-tmp 976M 2.8M 906M 1% /tmp
tmpfs 1.6G 0 1.6G 0% /run/user/0
tmpfs 1.6G 0 1.6G 0% /run/user/1009

One shows 100% used /dev/mapper/vg-root 101G 96G 0 100% /
could this be the problem? if so how to fix this? how do I know where file is trying to be written?
Could not set the file size of './ibtmp1'. Probably out of disk space
Yes, the problem is that your system patition ( mounted as / ) has no more space.
And on how to increase it, that on you. Thats the good thing about linux, there are a millions ways to do it. (But do something your comfortable with.)
 
Back
Top