Posts by UncleSam

UncleSam · Mar 2nd 2016

Hi,

if I try to update from 1.2.14 to 1.2.15 I get this error:
2016-03-02_20h09_29.png
2016-03-02_20h09_53.png

[ERROR] iMSCP::Stepper::step: Global symbol "$rs" requires explicit package name at /root/imscp/imscp-1.2.15/engine/PerlLib/Package/Webstats/Awstats/Uninstaller.pm line 101.
Global symbol "$rs" requires explicit package name at /root/imscp/imscp-1.2.15/engine/PerlLib/Package/Webstats/Awstats/Uninstaller.pm line 103.
Global symbol "$rs" requires explicit package name at /root/imscp/imscp-1.2.15/engine/PerlLib/Package/Webstats/Awstats/Uninstaller.pm line 104.
Compilation failed in require at /root/imscp/imscp-1.2.15/engine/PerlLib/Package/Webstats/Awstats/Awstats.pm line 94.

autoinstaller::Functions::install: An error occurred while performing installation steps

Can anyone help please?

UncleSam · Feb 25th 2016

Quote from Nuxwin

@UncleSam

If you do not want rerun installer, edit the /etc/imscp/imscp.conf file as stated by @Ninos and also the /etc/cron.d/imscp file. Change will be automatically detected by cron.

Thank you very much (both of you) - I try the installer less solution from Nuxwin.

UncleSam · Feb 25th 2016

Hallo,

is there any possibility to change the backup time? (I know there is a cron job but I have no idea if changing the time could be bad)

UncleSam · Feb 24th 2016

Hallo,

if you are using secure connections you can check your page at different pages (e.g. https://www.ssllabs.com/ssltest/) to get an grade (A+ till F). By harden your SSL connection of apache you always have to keep in your mind the mobile devices. Most of them are not able to use the best up2date secure options. So the key is to find the best secure solution to get a secure and reachable webpage.

Example SSLLabs test result: https://www.ssllabs.com/ssltest/analyze.html?d=inf-ro.de

I am running Ubuntu 14.04 LTS using I-MSCP 1.2.x. Inside /etc/apache2/mods-available/ssl.conf I changed the following lines to get an "A":

Code

SSLCipherSuite ECDHE-RSA-AES256-GCM-SHA384:HIGH:!MD5:!RC4:!DES:!MD5:!PSK:!aNULL:!eNULL:!EXPORT SSLHonorCipherOrder on SSLProtocol +TLSv1 +TLSv1.1 +TLSv1.2

And at the bottom I added:

Code

SSLCompression off
SSLUseStapling on
SSLStaplingResponderTimeout 5
SSLStaplingReturnResponderErrors off
#SSLStaplingCache "shmcb:logs/stapling-cache(150000)"
SSLStaplingCache "shmcb:${APACHE_RUN_DIR}/ssl_scache(512000)"
SSLStaplingResponseMaxAge 600

If you have a better knowledge base on how to secure apache2 ssl - please tell me/us. With this configuration every modern mobile device is able to connect as well as PCs.

Software which is not able to connect using my configuration:

IE 6 / XP
Java 6u45

To get an "A+" I think you just need to enable "HSTS": https://raymii.org/s/tutorials…e_NGINX_and_Lighttpd.html

UncleSam · Feb 23rd 2016

Hallo,

some days ago I needed a startup script based on screen. Killing the process on stop (like most of the scripts do) was not a solution. There should be a CTRL+C "keypress" to tell the process "please shutdown".
With this script you could modify your start and stop events as you need. Currently it is created to manage start and stop of sinusbot (TS3 MusikBot) - feel free to use it as you need (sinusbot post).
(At your own risk - no guarantee and no support!)

This script was made out of two ideas of creating a start / stop script:

Based on: https://github.com/fhd/init-script-template
Screen idea from: http://minecraft.gamepedia.com…als/Server_startup_script

How it works:
(Your could change start and stop behaviour by changing "sudo ..." and "sudo -u ..." lines)

Start
- Create an empty screen session
- Send to screen: switch to "dir" variable path
- Send to screen: "cmd" to start the program
Stop
- Sends to screen CTRL+C ('\003') and CTL+D ('\004'\) to stop process and log out from screen session
- Wait 10 seconds for the process to shut down and close screen session - if it takes more than 10 seconds -> kill the process (had no better idea )

Code

#!/bin/sh
### BEGIN INIT INFO
# Provides:
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start daemon at boot time
# Description: Enable service provided by daemon.
### END INIT INFO
name="sinusbot"
#name=`basename $0`
dir="/opt/ts3soundboard"
cmd="./sinusbot"
user="tsbots"
history=1024
pid_file="/var/run/$name.pid" # managed by root user starting the service
stdout_log="$dir/$name.log" # logfile has to be in a path where user has write permissions
stderr_log="$dir/$name.log" # logfile has to be in a path where user has write permissions
get_pid() {
if [ -z "$user" ]; then
sudo screen -ls | awk '/\.'$name'\t/ {print strtonum($1)}'
else
sudo -u "$user" screen -ls | awk '/\.'$name'\t/ {print strtonum($1)}'
fi
}
is_running() {
if [ -z "$user" ]; then
sudo screen -list | grep -q "$name"
else
sudo -u "$user" screen -list | grep -q "$name"
fi
}
case "$1" in
start)
if is_running; then
echo "Already started"
else
echo "Starting $name"
cd "$dir"
if [ -z "$user" ]; then
# start empty screen session
sudo screen -h $history -dmS $name &
# execute commands to start process
sudo screen -S $name -X stuff 'cd "'$dir'"'$(printf \\r)
sudo screen -S $name -X stuff $cmd' >> "'$stdout_log'" 2>> "'$stderr_log'"'$(printf \\r)
else
# start empty screen session
sudo -u "$user" screen -h $history -dmS $name &
# execute commands to start process
sudo -u "$user" screen -S $name -X stuff 'cd "'$dir'"'$(printf \\r)
sudo -u "$user" screen -S $name -X stuff $cmd' >> "'$stdout_log'" 2>> "'$stderr_log'"'$(printf \\r)
fi
for i in `seq 10`
do
if is_running; then
echo "is running"
break
fi
echo -n "."
sleep 1
done
if ! is_running; then
echo "Unable to start, see $stdout_log and $stderr_log"
exit 1
fi
fi
;;
stop)
if is_running; then
echo -n "Stopping $name.."
if [ -z "$user" ]; then
sudo screen -S $name -X stuff '\003' > /dev/null 2>&1
sudo screen -S $name -X stuff '\004' > /dev/null 2>&1
else
sudo -u "$user" screen -S $name -X stuff '\003' > /dev/null 2>&1
sudo -u "$user" screen -S $name -X stuff '\004' > /dev/null 2>&1
fi
for i in `seq 10`
do
if ! is_running; then
break
fi
if [ -z "$user" ]; then
#sudo screen -S $name -X stuff '\003' > /dev/null 2>&1
sudo screen -S $name -X stuff '\004' > /dev/null 2>&1
else
#sudo -u "$user" screen -S $name -X stuff '\003' > /dev/null 2>&1
sudo -u "$user" screen -S $name -X stuff '\004' > /dev/null 2>&1
fi
echo -n "."
sleep 1
done
echo
if is_running; then
kill `get_pid`
fi
if is_running; then
echo "Not stopped; may still be shutting down or shutdown may have failed"
exit 1
else
echo "Stopped"
fi
else
echo "Not running"
fi
;;
restart)
$0 stop
if is_running; then
echo "Unable to stop, will not attempt to start"
exit 1
fi
$0 start
;;
status)
if is_running; then
echo "Running"
else
echo "Stopped"
exit 1
fi
;;
*)
echo "Usage: $0 {start|stop|restart|status}"
exit 1
;;
esac
exit 0

Display More

UncleSam · Feb 23rd 2016

Quote from Nuxwin

@UncleSam

In the package file for Trusty,try to add <package>mysql-common</package> into the mariadb 10.0 section and run the installer again.

See https://github.com/i-MSCP/imsc…/packages-trusty.xml#L137

Installation worked now for me - thanks for your help.

Quote from Nuxwin

PLease, don'r run 1.2.11 installer if you have run the 1.2.12 installer (downgrading is not supported). I need some minutes to try with trusty and mariadb 10.0

Yes I know this and I had a backup of everything. But it seemd to be safe if the problem was at "Checking requirements" section.

UncleSam · Feb 23rd 2016

Update:
I checked it more than twice, the 1.2.11 installer works fine for me, 1.2.12 uninstalls mariadb everytime I call the installer.

UncleSam · Feb 23rd 2016

I installed mariadb manual and did I-MSCP installer again: (After installing mariadb it seems all worked again)
2016-02-23_21h58_41.png
Translated: Preparing to remove mariadb-server10.0 completely.

UncleSam · Feb 23rd 2016

Distro: Ubuntu Server LTS 14.04
Codname: sry no idea what info you need here (Ubutnu 14.04 Codename: 14.04.4 LTS, Trusty Tahr)
MariaDb: I installed with I-MSCP the version 10 but no idea what version number it was in detail

(Teamviewer available if needed)

UncleSam · Feb 23rd 2016

Hallo,

I tried to update from 1.2.11 to 1.2.12 and all I got was a Error during requirements check:
2016-02-23_21h38_38.png

No idea what is down at the moment but admin panel and all webpages are not available. Seems like update uninstalled my Mariadb. Can anyone please help me?

Posts by UncleSam

Update 1.2.14 to 1.2.15

Change backup time

Change backup time

Harden Apache2 SSL

Server Start Stop using screen

Upgrade 1.2.11 to 1.2.12 broken

Upgrade 1.2.11 to 1.2.12 broken

Upgrade 1.2.11 to 1.2.12 broken

Upgrade 1.2.11 to 1.2.12 broken

Upgrade 1.2.11 to 1.2.12 broken