Installing the agent
-
@scottalanmiller said in Installing the agent:
For Mac the installer should work fine, I believe. It's pretty new. For scanning, we are working on getting it to keep reporting. It keeps working, but acts like it isn't. So it collects data, but says that the data is old.
Should the Mac at least check in once?
-
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
For Mac the installer should work fine, I believe. It's pretty new. For scanning, we are working on getting it to keep reporting. It keeps working, but acts like it isn't. So it collects data, but says that the data is old.
Should the Mac at least check in once?
Yes, it "should".
-
Installing on Debian 8.8
root@library:~# wget -q -O - https://gitlab.com/dutchcolonial/sodiumsuiteinstallers/raw/master/unix.sh | bash -s 79bcd200ab29ef4fac4adc5a34ff0a9b7d065146 Hit http://security.debian.org jessie/updates InRelease Ign http://ftp.us.debian.org jessie InRelease Get:1 http://ftp.us.debian.org jessie-updates InRelease [145 kB] Hit http://security.debian.org jessie/updates/main Sources Hit http://security.debian.org jessie/updates/main amd64 Packages Hit http://ftp.us.debian.org jessie Release.gpg Hit http://security.debian.org jessie/updates/main Translation-en Hit http://ftp.us.debian.org jessie Release Hit http://ftp.us.debian.org jessie-updates/main Sources Get:2 http://ftp.us.debian.org jessie-updates/main amd64 Packages/DiffIndex [10.9 kB] Get:3 http://ftp.us.debian.org jessie-updates/main Translation-en/DiffIndex [3,688 B] Hit http://ftp.us.debian.org jessie/main Sources Hit http://ftp.us.debian.org jessie/main amd64 Packages Hit http://ftp.us.debian.org jessie/main Translation-en Fetched 160 kB in 2s (63.0 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: dctrl-tools debconf debconf-i18n debconf-utils libpgm-5.1-0 libsodium13 libzmq3 python-jinja2 python-m2crypto python-mako python-markupsafe python-msgpack python-yaml python-zmq salt-common Suggested packages: debtags debconf-doc libterm-readline-gnu-perl libgtk2-perl libnet-ldap-perl libqtgui4-perl libqtcore4-perl python-jinja2-doc python-beaker python-mako-doc salt-doc python-augeas The following NEW packages will be installed: dctrl-tools debconf-utils libpgm-5.1-0 libsodium13 libzmq3 python-jinja2 python-m2crypto python-mako python-markupsafe python-msgpack python-psutil python-yaml python-zmq salt-common salt-minion The following packages will be upgraded: debconf debconf-i18n 2 upgraded, 15 newly installed, 0 to remove and 127 not upgraded. 2 not fully installed or removed. Need to get 0 B/3,641 kB of archives. After this operation, 13.3 MB of additional disk space will be used. Reading changelogs... Done Preconfiguring packages ... Setting up udev (215-17+deb8u7) ... addgroup: The group `input' already exists as a system group. Exiting. update-initramfs: deferring update (trigger activated) insserv: warning: script 'K00ezproxy' missing LSB tags and overrides insserv: warning: script 'ezproxy' missing LSB tags and overrides insserv: There is a loop between service ezproxy and mountnfs if started insserv: loop involving service mountnfs at depth 5 insserv: loop involving service nfs-common at depth 4 insserv: There is a loop between service rc.local and mountall if started insserv: loop involving service mountall at depth 6 insserv: loop involving service checkroot-bootclean at depth 5 insserv: There is a loop between service rc.local and urandom if started insserv: loop involving service urandom at depth 7 insserv: There is a loop between service ezproxy and mountdevsubfs if started insserv: loop involving service mountdevsubfs at depth 2 insserv: loop involving service udev at depth 1 insserv: There is a loop at service rc.local if started insserv: There is a loop between service ezproxy and rc.local if started insserv: loop involving service rc.local at depth 3 insserv: loop involving service ezproxy at depth 2 insserv: loop involving service rsyslog at depth 1 insserv: There is a loop between service ezproxy and mountall-bootclean if started insserv: loop involving service mountall-bootclean at depth 1 insserv: loop involving service kbd at depth 12 insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: loop involving service mountnfs-bootclean at depth 12 insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: loop involving service networking at depth 9 insserv: loop involving service hwclock at depth 4 insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting ezproxy depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Max recursions depth 99 reached insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header dpkg: error processing package udev (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for initramfs-tools (0.120+deb8u2) ... update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64 Errors were encountered while processing: udev E: Sub-process /usr/bin/dpkg returned an error code (1) bash: line 29: uuidgen: command not found Failed to restart salt-minion.service: Unit salt-minion.service failed to load: No such file or directory. Failed to execute operation: No such file or directory``` -
And on Windows 2008 R2 using the SuperDOS script:
-
@wls-itguy looks like you have a problem with your system and insserve. I've seen it recommended to remove it as too many things don't support it.
apt-get remove insserv -
@scottalanmiller said in Installing the agent:
@wls-itguy looks like you have a problem with your system and insserve. I've seen it recommended to remove it as too many things don't support it.
apt-get remove insservNot sure if I can as I might need it for the EZ Proxy part that is on that server. But I'll see what I can do.
-
@wls-itguy said in Installing the agent:
And on Windows 2008 R2 using the SuperDOS script:
PowerShell doesn't have Invoke-Webrequest? That's a really old cmdlet. I noticed the Debian system having issues is not patched, is this Windows maybe not patched either? We can always get the script another way, but not having PowerShell makes it a little harder.
-
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy looks like you have a problem with your system and insserve. I've seen it recommended to remove it as too many things don't support it.
apt-get remove insservNot sure if I can as I might need it for the EZ Proxy part that is on that server. But I'll see what I can do.
EZ Proxy is specifically one of the packages not working with it.
-
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
And on Windows 2008 R2 using the SuperDOS script:
PowerShell doesn't have Invoke-Webrequest? That's a really old cmdlet. I noticed the Debian system having issues is not patched, is this Windows maybe not patched either? We can always get the script another way, but not having PowerShell makes it a little harder.
Had to restore the debian system from backup. I'll patch it before I try installing the SS agent again.
The Windows box didn't have any updates needed.
-
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
And on Windows 2008 R2 using the SuperDOS script:
PowerShell doesn't have Invoke-Webrequest? That's a really old cmdlet. I noticed the Debian system having issues is not patched, is this Windows maybe not patched either? We can always get the script another way, but not having PowerShell makes it a little harder.
Had to restore the debian system from backup. I'll patch it before I try installing the SS agent again.
Just now?
-
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
And on Windows 2008 R2 using the SuperDOS script:
PowerShell doesn't have Invoke-Webrequest? That's a really old cmdlet. I noticed the Debian system having issues is not patched, is this Windows maybe not patched either? We can always get the script another way, but not having PowerShell makes it a little harder.
Had to restore the debian system from backup. I'll patch it before I try installing the SS agent again.
Just now?
Yes.
-
@wls-itguy said in Installing the agent:
The Windows box didn't have any updates needed.
Very strange that PS doesn't have that cmdlet when updated.
If PowerShell is too hold for the job, you can use the fallback manual download:
Once downloaded, open the folder it is in, right click and "Run As Admin"
-
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
And on Windows 2008 R2 using the SuperDOS script:
PowerShell doesn't have Invoke-Webrequest? That's a really old cmdlet. I noticed the Debian system having issues is not patched, is this Windows maybe not patched either? We can always get the script another way, but not having PowerShell makes it a little harder.
Had to restore the debian system from backup. I'll patch it before I try installing the SS agent again.
Just now?
Yes.
That's not good. Those errors don't appear to be from the install, though, they appear to be from existing packages that can't update.
-
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
And on Windows 2008 R2 using the SuperDOS script:
PowerShell doesn't have Invoke-Webrequest? That's a really old cmdlet. I noticed the Debian system having issues is not patched, is this Windows maybe not patched either? We can always get the script another way, but not having PowerShell makes it a little harder.
Had to restore the debian system from backup. I'll patch it before I try installing the SS agent again.
Just now?
Yes.
That's not good. Those errors don't appear to be from the install, though, they appear to be from existing packages that can't update.
Yea, that thing is FUBAR'd! Guess I have something else to work on tomorrow
-
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
And on Windows 2008 R2 using the SuperDOS script:
PowerShell doesn't have Invoke-Webrequest? That's a really old cmdlet. I noticed the Debian system having issues is not patched, is this Windows maybe not patched either? We can always get the script another way, but not having PowerShell makes it a little harder.
Powershell versions did not update with Windows Update by default in 2008 R2 to my knowledge.
-
@jaredbusch said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
And on Windows 2008 R2 using the SuperDOS script:
PowerShell doesn't have Invoke-Webrequest? That's a really old cmdlet. I noticed the Debian system having issues is not patched, is this Windows maybe not patched either? We can always get the script another way, but not having PowerShell makes it a little harder.
Powershell versions did not update with Windows Update by default in 2008 R2 to my knowledge.
It doesn't. Just read that on the Google. I am updating now.
-
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
And on Windows 2008 R2 using the SuperDOS script:
PowerShell doesn't have Invoke-Webrequest? That's a really old cmdlet. I noticed the Debian system having issues is not patched, is this Windows maybe not patched either? We can always get the script another way, but not having PowerShell makes it a little harder.
Had to restore the debian system from backup. I'll patch it before I try installing the SS agent again.
Just now?
Yes.
That's not good. Those errors don't appear to be from the install, though, they appear to be from existing packages that can't update.
Yea, that thing is FUBAR'd! Guess I have something else to work on tomorrow
So it definitely has problems even on the restore without any SS on there? Not that I'm happy about that, but sure didn't want to be the cause of any problems.
-
Googled to verify..
Invoke-Webrequestwas implemented with Powershell 3.0 in 2012.That is after Server 2008 R2.
-
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
And on Windows 2008 R2 using the SuperDOS script:
PowerShell doesn't have Invoke-Webrequest? That's a really old cmdlet. I noticed the Debian system having issues is not patched, is this Windows maybe not patched either? We can always get the script another way, but not having PowerShell makes it a little harder.
Had to restore the debian system from backup. I'll patch it before I try installing the SS agent again.
Just now?
Yes.
That's not good. Those errors don't appear to be from the install, though, they appear to be from existing packages that can't update.
Yea, that thing is FUBAR'd! Guess I have something else to work on tomorrow
So it definitely has problems even on the restore without any SS on there? Not that I'm happy about that, but sure didn't want to be the cause of any problems.
Correct. Seems there are some other things going sideways on that box. Good thing it is only a Proxy server. I'll spin up a new VM for it and move the limited data over tomorrow.
-
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
@scottalanmiller said in Installing the agent:
@wls-itguy said in Installing the agent:
And on Windows 2008 R2 using the SuperDOS script:
PowerShell doesn't have Invoke-Webrequest? That's a really old cmdlet. I noticed the Debian system having issues is not patched, is this Windows maybe not patched either? We can always get the script another way, but not having PowerShell makes it a little harder.
Had to restore the debian system from backup. I'll patch it before I try installing the SS agent again.
Just now?
Yes.
That's not good. Those errors don't appear to be from the install, though, they appear to be from existing packages that can't update.
Yea, that thing is FUBAR'd! Guess I have something else to work on tomorrow
So it definitely has problems even on the restore without any SS on there? Not that I'm happy about that, but sure didn't want to be the cause of any problems.
Correct. Seems there are some other things going sideways on that box. Good thing it is only a Proxy server. I'll spin up a new VM for it and move the limited data over tomorrow.
See, SodiumSuite found your first issue already!
