Tried 4 times to install but keep getting error kimsufi


#1

Hi

ive been trying with 3 fresh installs and i keep getting errors after install something to do with apache2 but when i try to refresh using service i get

movh2:~# service apache2 restart
Failed to restart apache2.service: Unit apache2.service not found.

This site can’t be reached

xx.xxx.xx.xxx refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED

never had this before its a kimsufi server running Ubuntu Server 16.10 “Yakkety Yak” (NEW) (64bits)

i did see an error it said something like ip-tables not found line 120 of quickbox missing or something missed it

cant work it out any help be appreciated

thanks


#2

Obviously you know how this works as a long-time user of QuickBox :heart:

  • You’re installing in /root directory (don’t guff me @coaster, I know you know this :P)
  • Can you do an apt -y update and see what the return is? I bet money it errors out and there is a dependency lock.

I have noticed this with 16.10 only on certain hosts (OVH and Kimsufi … random Hetzner machines also) where the dependencies are broken as I think a lot of maintainers are changing and/or haven’t updated their repos to work with 16.10 … which is technically experimental at any rate and I may had been hasty including it in QuickBox :sweat:

###Post Script

What’s interesting is I have seen that error before… same line and everything. However; the installer doesn’t call on iptables for blocking port 1900 (b/c it’s a QuickBox courtesy of course to block nefarious ports magically) until line 205

# This function blocks an insecure port 1900 that may lead to
# DDoS masked attacks. Only remove this function if you absolutely
# need port 1900. In most cases, this is a junk port.
function _ssdpblock() {
  iptables -I INPUT 1 -p udp -m udp --dport 1900 -j DROP
}

#3

hi

it seemed to go ok

Hit:1 http://archive.canonical.com/ubuntu yakkety InRelease
Hit:2 http://archive.ubuntu.com/ubuntu yakkety InRelease
Get:3 http://archive.ubuntu.com/ubuntu yakkety-security InRelease [102 kB]
Hit:4 http://ppa.launchpad.net/ondrej/php/ubuntu yakkety InRelease
Get:5 http://archive.ubuntu.com/ubuntu yakkety-updates InRelease [102 kB]
Get:6 http://archive.ubuntu.com/ubuntu yakkety-backports InRelease [102 kB]
Get:7 http://archive.ubuntu.com/ubuntu yakkety-updates/universe Sources [27.9 kB]
Get:8 http://archive.ubuntu.com/ubuntu yakkety-updates/main i386 Packages [157 kB]
Get:9 http://archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages [159 kB]
Get:10 http://archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 Packages [86.0 kB]
Get:11 http://archive.ubuntu.com/ubuntu yakkety-updates/universe i386 Packages [83.6 kB]
Fetched 821 kB in 1s (675 kB/s)
Reading package lists… Done
Building dependency tree
Reading state information… Done
1 package can be upgraded. Run ‘apt list --upgradable’ to see it.
movh2:~# apt-get -f upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Correcting dependencies… Done
Calculating upgrade… Done
The following NEW packages will be installed:
update-notifier-common
The following packages will be upgraded:
openssl
1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
329 not fully installed or removed.
Need to get 684 kB/846 kB of archives.
After this operation, 1,608 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ppa.launchpad.net/ondrej/php/ubuntu yakkety/main amd64 openssl amd64 1.0.2j-1+deb.sury.org~yakkety+1 [684 kB]
Fetched 684 kB in 0s (4,456 kB/s)
(Reading database … 60168 files and directories currently installed.)
Preparing to unpack …/0-update-notifier-common_3.175.1_all.deb …
Unpacking update-notifier-common (3.175.1) …
dpkg: error processing archive /tmp/apt-dpkg-install-rRlaQm/0-update-notifier-common_3.175.1_all.deb (–unpack):
trying to overwrite ‘/etc/apt/apt.conf.d/10periodic’, which is also in package apt-config-auto-update 2.0.0-1ubuntu1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to unpack …/1-openssl_1.0.2j-1+deb.sury.org~yakkety+1_amd64.deb …
Unpacking openssl (1.0.2j-1+deb.sury.org~yakkety+1) over (1.0.2g-1ubuntu9) …
Errors were encountered while processing:
/tmp/apt-dpkg-install-rRlaQm/0-update-notifier-common_3.175.1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


#4

That is your issue. What does cat /etc/apt/apt.conf.d/ show?


#5

cat: /etc/apt/apt.conf.d/: Is a directory

movh2:~# cat /etc/apt/apt.conf.d/10periodic
APT::Periodic::Update-Package-Lists “1”;
APT::Periodic::Download-Upgradeable-Packages “0”;
APT::Periodic::AutocleanInterval “0”;

i dont understand why it is doing this tbh your script works flawlessly on oneprovider servers but not so on kimsufi running the same OS do they do something to stop scripts being installed


#6

@coaster did you install ubuntu with the stock kernel on the kimsurfi the kimsurfi boxes along with all soyoustart, OVH boxes default to a custom OVH kernel that tends to screw stuff up and other weird things .


#7

I’ve already ran into this on about 4 OVH Guru Installs. The problem is that file in the /etc/apt/apt.conf.d/ directory having a bad/expired extension name not for use on the ap update and upgrade… so more than likely it fails. If you just issue a mv on that file to say 10periodicyadayadayada.BAK and then run your updater, all is well.

Not sure when or why this is suddenly on default OVH installs.

Anyone else having that issue… just move that file to a .BAK extension, then run apt -y update && apt -y upgrade and run the QuickBox install commands (just the bash /root/QuickBox/setup/quickbox-setup bit) to fix and/or complete the install.


#8

Hi

thanks for solving this JM i did manage to solve the situation myself by getting rid of OVH

something weird going on over there i have a few websites hosted there on VPS servers and they decided to just suspend it and the only cure was to reinstall the OS something about security breach on their network its just simple html one page websites lol

better the devil you know i will be sticking with oneprovider a bit rough around the edges but they work

thanks again