Error while Installing DirectAdmin on a Digital Ocean droplet - digital-ocean

I was installing DA on a Digital Ocean droplet then I ran into an error :
virtual memory exhausted: Cannot allocate memory
make: *** [ext/fileinfo/libmagic/apprentice.lo] Error 1
Changed secure_php option from no to yes
PHP has been secured.
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
I have a personal DA license and my DigitalOcean droplet is 1GB Memory/ 25GB Disk and using CentOS 7.6 64bits.
I've been stucking at this error for about 3 hours and still don't know what to do next, please help me out, thank you.

I solved it !
Turned out, I need to add more ram or create swap. So I did create swap on my vps and then I reinstalled DA, then everything worked perfectly.
Hope this will help anybody running into the same prolem like me.

Related

openSUSE-2022-10067 - Failed to open a session for the virtual machine

After installing openSUSE-2022-10067 Security update for virtualbox, I got the following error when trying to start a guest vitural machine: Failed to open a session for the virtual machine. Result Code NS_ERROR_FAILURE (0x80004005) Component: SessionMachine Interface: ISession{c0447716-ff5a-4795-b57a-ecd5fffa18a4}
Details: The VM Session was aborted.
I had above errors with MS Win-10 and Opensuse Leap 15.4 Guest VM's on a Open Suse Leap 15.4 VM-Host-System.
Anybody experiances the same issue?
My temporary solution was to rollback the snapshot to pre-installation of the security update for virtualbox. Then it was possible to start the VM's without any errors again.
I think I've seen a similar crash when trying to start a VM with the combination of VirtualBox 6.1.35 and 6.1.36 in combination with the VirtualBox Extension Pack (EP) 6.1.34. Did you also upgrade the EP? ;)
This solves my problem in VirtualBox 6.1.36
With 6.1.35 I could not even update the EP without running in the same error.
Hope this helps.
BR Markus

AWS EC2 - FTP return error 451 when trying to upload new file

I am running two t2.medium EC2 servers on AWS. They are both launched from the same AMI and with similar settings, FTP (except passwords ofc) and locations. The only difference in the two servers is the content in the /var/www/html folder.
So far they have been working as expected but yesterday something weird started happening. Whenever I try to upload a new version of a (php) file on one of the servers, it fails and returns the error "server did not report OK, got 451". I've tried different FTP-users, different IDEs and rebooting my EC2-server without any luck. This only happens on one of the servers and it started happening "out of the blue"
Any suggestions how to fix this or at least in what direction I should continue my debugging?
The comment by #korgen lead me to the error log of the server. When I ran sudo less /var/log/secure I quickly saw the error message: error:
Failed to write to /var/log/btmp: No space left on device
I checked the storage volume by running the command df -h and I saw that 20.0 / 20.0 GB was in use. I increased the server volume size in AWS and after a quick reboot it all now works again.
I hope this helps a future lost soul :-)

Unable to install devstack in Virtual Box

I followed the steps below, but I'm getting an error.
Install Virtual Box (version 5.0.0) running on Windows 7 host machine.
Install Ubuntu server version 14.04.02 on it.
git clone https://github.com/openstack-dev/devstack.git
cd devstack; cp samples/local.conf .
After that i ran ./stack.sh but came with this error after running for approx 30 minutes:
2015-07-21 20:04:18.841 | ERROR (ConnectionRefused): Unable to establish connection to 10.0.2.15:8774/v2/c199aa06389a4c8c85dffddad18fce1b/flavors/… 2015-07-21 20:04:20.433 | + exit 1 deb#Devstack:~/devstack$
Please help me in resolving the issue
Try re-running the stack. Thats the best hack i found for DevStack debugging.
You need to do some specific network settings in virtual box to overcome this error.
From the Network section, change Attached to to Bridged Adapter, Adapter Type to Paravirtualized Network (virtio-net) and Promiscuous Mode to Allow All.
Check Enable Nested VT-x/AMD-v from System > Processor .
Select USB Tablet as the Pointing Device from System > Motherboard.
Then restart the virtual machine and check ifconfig for a new IP, add it in local.conf and then try install script again.
It should work this time :-)

Applying coldfusion 8 Update 1

I'm running ColdFusion 8 Enterprise Edition on RHEL 4 32bit. I tried applying the ColdFusion 8 Update 1 (8.0.1) but the installation fails with the error below. Can anyone help?
Thank you.
===============================================================================
Installing...
===============================================================================
Installation Aborted
The installation of the Adobe ColdFusion 8.0.1 did not complete successfully.
Please make sure that the ColdFusion MX server has been shut down prior to
running the installer again.
All services related to coldfusion, webserver, jrun are stopped alerady.
I do not know about Red Hat but if you get this error on Windows then you need to stop all the JRun services to complete the update.
This article here has a section on starting a CF service on Linux http://www.aaronwest.net/blog/index.cfm/2011/2/7/Super-Guide-Installing-ColdFusion-9-on-CentOS-Linux I am pretty sure if you substitute start for stop in that command you might have some joy.

Unable to determine guest operating system: Vmware error

Ok, here's a very short and to the point question. When trying to import a virtual PC 2004 Windows 2003 Server VM in VM Workstation 6.0.2 I'm getting an error 'unable to determine guest operating system'. Soo how to fix?
From here:
Make sure that that the VM is not currently running in VMware Server.
Make sure that VMware Server does not have a lock on the VM’s files. You have have to stop all VMware Server Services and/or reboot the (VMWare) server.
Make sure you have appropriate permissions to the VM’s files.
This is a fairly generic error from VMware Converter so I would try the following:
Step 1. Make sure you are running the latest version of VMware Converter. Updates seem to come pretty often for this tool.
Step 2. Check the VMware Converter log file. More often than not you will find the source of your problem here.