It will take some time: 30 minutes - 1 hour.
When you are asked questions answer the default, press enter or "q" key when you must read long info pages.
2) Update Scrollout /var/www/bin/update.sh force
From: Anders Nordh
Sent: Thursday, March 22, 2018 4:44 PM
To: marius.gologan@gmail.com
Subject: [scrollout:discussion] Update failed, problem with php?
Hi, Debian GNU/Linux 8 \n \l
I have installed your ISO image and then only upgraded as I tried today.
Kindly,
Anders
No problem wtih the OS upgrade.
But during the
/var/www/bin/update.sh force
Fail2ban installation or configuration run in loop and never finish.
mars 23 20:01:46 Zeus systemd[1]: Failed to start Fail2Ban Service.
mars 23 20:01:46 Zeus systemd[1]: fail2ban.service: Unit entered failed state.
mars 23 20:01:46 Zeus systemd[1]: fail2ban.service: Failed with result 'exi…de'.
Hint: Some lines were ellipsized, use -l to show in full.
● fail2ban.service - Fail2Ban Service
Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2018-03-23 20:29:44 CET; 9ms ago
Docs: man:fail2ban(1)
Process: 7529 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)
dpkg: erreur de traitement du paquet fail2ban (--configure) :
le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Des erreurs ont été rencontrées pendant l'exécution :
fail2ban
E: Sub-process /usr/bin/dpkg returned an error code (1)
dpkg: erreur: cannot access archive '/tmp/scrolloutf1/www/cfg/geo/libip-country-perl_2.27-1_all.deb': Aucun fichier ou dossier de ce type
Lecture des listes de paquets... Fait
After 1hour he finished the upgrade, but i m not sure about the state of Scrollout.
Best regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi guys, thanks for helping me/us out.
I went for a fresh install using the present iso file, updated the scrollout installation and now I am fine again.
Thanks,
Anders
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Fresh Install from ISO on the sourcefroge repo.
When i mount iso he prompt me to install in graphical mode, seems strange. Like a normal debian with no pakages
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Fresh Install from ISO on the sourcefroge repo.
When i mount iso he prompt me to install in graphical mode, seems strange. Like a normal debian with no pakages
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Marius, if you read this there seem to be an issue between Debian 9, Scrollout and VMWare Player 14, latest release. When using "Reboot" from the Scrollout GUI the network interface always fail after reboot and a total reboot of the server running VMWare guests is required for the interface to be found again. Sometimes a reboot (shutdown -r) from the host itself render the same problem.
Regards,
Anders
Last edit: Anders Nordh 2018-03-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, just run a "/var/www/bin/update.sh force" and after that I run into php issues and cannot access the web gui.
sed: can't read /etc/php/"star"/fpm/php.ini: No such file or directory
"star" = *
Any ideas, and please note that I am no pro when it comes to Linux ... ;-)
Thanks,
Anders!
Last edit: Anders Nordh 2018-03-22
Hi,
Try to update again and see if fixes you problem.
Marius.
Sorry ´Marius, same issue but thanks for trying ...
Have a nice day,
Anders
Hi, tried again and during update at the end of reading the package list I get
sed: can't read /etc/php/"asterisk"/fpm/php.ini: No such file or directory
And after reboot I barely see a message saying something about not starting the web server ... ish ...
Please advice.
//Anders
Try these:
apt-get install php -y
php -v
Should return version 7.
On Thu, Mar 22, 2018, 11:41 Anders Nordh andersnordh@users.sourceforge.net
wrote:
Hi, the first command get "Unable to locate package php" and the version report back PHP 5.6.33 ...
Kindly,
Anders
Please post here the version of your OS by running:
cat /etc/issue
On Thu, Mar 22, 2018, 15:14 Anders Nordh andersnordh@users.sourceforge.net
wrote:
Hi, Debian GNU/Linux 8 \n \l
I have installed your ISO image and then only upgraded as I tried today.
Kindly,
Anders
1) Upgrade from Debian 8 to Debian 9
It will take some time: 30 minutes - 1 hour.
When you are asked questions answer the default, press enter or "q" key when you must read long info pages.
2) Update Scrollout
/var/www/bin/update.sh forceFrom: Anders Nordh
Sent: Thursday, March 22, 2018 4:44 PM
To: marius.gologan@gmail.com
Subject: [scrollout:discussion] Update failed, problem with php?
Hi, Debian GNU/Linux 8 \n \l
I have installed your ISO image and then only upgraded as I tried today.
Kindly,
Anders
Update failed, problem with php?
Sent from sourceforge.net because marius.gologan@gmail.com is subscribed to https://sourceforge.net/p/scrollout/discussion/1102835/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/scrollout/admin/discussion/forums. Or, if this is a mailing list, you can unsubscribe from the mailing list.
Last edit: Marius Gologan 2018-03-22
Hi Marius,
No problem wtih the OS upgrade.
But during the
/var/www/bin/update.sh force
Fail2ban installation or configuration run in loop and never finish.
mars 23 20:01:46 Zeus systemd[1]: Failed to start Fail2Ban Service.
mars 23 20:01:46 Zeus systemd[1]: fail2ban.service: Unit entered failed state.
mars 23 20:01:46 Zeus systemd[1]: fail2ban.service: Failed with result 'exi…de'.
Hint: Some lines were ellipsized, use -l to show in full.
● fail2ban.service - Fail2Ban Service
Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2018-03-23 20:29:44 CET; 9ms ago
Docs: man:fail2ban(1)
Process: 7529 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)
dpkg: erreur de traitement du paquet fail2ban (--configure) :
le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Des erreurs ont été rencontrées pendant l'exécution :
fail2ban
E: Sub-process /usr/bin/dpkg returned an error code (1)
dpkg: erreur: cannot access archive '/tmp/scrolloutf1/www/cfg/geo/libip-country-perl_2.27-1_all.deb': Aucun fichier ou dossier de ce type
Lecture des listes de paquets... Fait
After 1hour he finished the upgrade, but i m not sure about the state of Scrollout.
Best regards
Hi guys, thanks for helping me/us out.
I went for a fresh install using the present iso file, updated the scrollout installation and now I am fine again.
Thanks,
Anders
hi Anders,
After install the fresh iso from scrollout repo, did you install scrollout ? or juste made an update ?
or Both ^^
Hi, did the fresh install and then only /var/www/bin/update.sh force ...
Fresh Install from ISO on the sourcefroge repo.
When i mount iso he prompt me to install in graphical mode, seems strange. Like a normal debian with no pakages
Fresh Install from ISO on the sourcefroge repo.
When i mount iso he prompt me to install in graphical mode, seems strange. Like a normal debian with no pakages
Well, had the same choice but opted for the normal one instead.
//Anders
Hi Marius, if you read this there seem to be an issue between Debian 9, Scrollout and VMWare Player 14, latest release. When using "Reboot" from the Scrollout GUI the network interface always fail after reboot and a total reboot of the server running VMWare guests is required for the interface to be found again. Sometimes a reboot (shutdown -r) from the host itself render the same problem.
Regards,
Anders
Last edit: Anders Nordh 2018-03-23
Hi Anders, The network interface itself is not failing. It is something to do with the custom script that starts up the interface.
As a temporary work around while Marius fixes it, you can make a simple modification to /etc/network/interfaces
Add the line 'auto eth0' to the primary network interface section like below
# The primary network interface
auto eth0
allow-hotplug eth0
iface eth0 inet static
mtu 1492
address 192.168.xxx.xxx
netmask 255.255.255.0
gateway 192.168.xxx.xxx
dns-nameservers 192.168.xxx.xxx
Last edit: M2G Admin 2018-04-03
Hi,
I think I managed to identify the bug and fix it minutes ago.
Thank you all for reporting this issue.