We have 6 year old interworx installation ( Centos 5, PHP 5.2, … ).
We want migrate this server to Centos 7, PHP 5.4, etc …
I make backup on old iworx, with backup.pex or siteworx backup function
Or if i use nodeworx import over SSH function.
If we use this backups, some domain import is failed (not all, we have 300+ domain, 20-30 have a problem)
proc_nice(): Only a super user may attempt to increase the priority of a process
A system error has occurred. Please try your request again in a few minutes.
If the error persists, please contact support.
Reverting Backup Directory : xxxxxx
Have you tried FTP the siteworx backup to new server, unpacking it to tar (gunzip filename), then telling import to use this file on local system
Can you create a structure only back up, restore this structure to create the siteworx account, then login to the siteworx account, then perform the restore from the unpacked tar backup held locally
I hope it helps but if needed quickly, I would open a support ticket with your license provider
I found it one interesting …
those backups do not run, in what there is an SQL backup.
All backups (small or large) is done if does not contain SQL database.
If backup have SQL database, backup dont finish.
system informations:
old system:
Centos 5.11 (XenServer 6 VM)
iworx 5.1.13
mysql Ver 14.12 Distrib 5.0.95
new system:
Centos 7 (LXC container - proxmox host, ZFS FS)
iworx 5.1.13
mysql Ver 15.1 Distrib 5.5.47-MariaDB
I had a similar issue when mass importing and a few would not complete at first, but IW resolved it very quickly
I think your import would work as expected if you create a structure only backup, then create the siteworx account on the new server, login to the siteworx account, restore structure only backup, then restore full backup, or partial backup
I think this is where the issue is, as it is looking for the siteworx user as the superuser and not root
If you do a ulimit command this shows if any limit thats been set on processes, This can be a value from 0 to 40, the greater that number, the higher the priority a user can set for a process
By default Centos/Redhat has a limit of 1024 or 4096 - which is pretty low, if a large import is happening this should probably be set to something higher.
If you do a ulimit -n it will show the current limit.
If you want to increase it to (lets say to 40000).
You need to edit “/etc/sysctl.conf” and put fs.file-max=40000.
fs.file-max = 40000
You also need to edit /etc/security/limits.conf and updated hard (Hn) and soft values (Sn).
Added following lines in /etc/security/limits.conf:
soft nofile 40000
hard nofile 40000
add following line in /etc/pam.d/su-
session required pam_limits.so
By default RHEL/CentOS from what i remember had 1024 by default but changed it to 4096 later. There are some server images that have the image configured the ulimit to unlimited, so it depends really.
its okay.
This did not solve the problem unfortunately, import is failed:
…
Database was imported : barbara
proc_nice(): Only a super user may attempt to increase the priority of a process
A system error has occurred. Please try your request again in a few minutes.
If the error persists, please contact support.
…
Very important, we run interworx in LXC container!
e.g: do not modify fs.file-max kernel parameter, but, file-max is kernel setting is ok:
sysctl -a | grep file-max
fs.file-max = 3283152
In LXC container we dont have any problem with interworx (or other stuff)
Proxmox 4.2, current kernel: 4.4.8-1
If I have time, i make simple test, we make this test system on KVM virtualization (non LXC), if import ok, this is LXC generated problem. (we waiting demo interworx licenc key)
and backup import is successfully.
No errors, and not stopped.
We use many applications on LXC container, without problems.
What may be the trouble ?
if i turn on full debug on iworx, no more information whats wrong.
we have little time to migration sites from old iworxs installations to new servers and installs. by hand import is not good.
