Error in update.sh / twisted install #34
Comments
|
thx. I guess another dependency that needs to be addressed. |
|
interesting ... pls have a look at this thread and report if it helped: |
|
I tried the: sudo find /usr -name '*.pyc' -delete and ran again. I selected to reinstall mySQL in the options. Got the following abort: |
|
can't reproduce on my end ... pls try: sudo /etc/init.d/cowrie stop and provide the output, thanks. |
|
Here's the output (I did change the '.pyc' to '*.pyc' in the above commands. |
|
Maybe the pip.log will help... |
|
maybe you can try to update setuptools: sudo pip install setuptools --upgrade then pls retry: fingers crossed |
|
for the record: here is my list: appdirs (1.4.3) |
|
Sigh.. no joy :( |
|
just guessing: and |
|
Mine shows |
|
I'm going to try a fresh install from 2017-02-16-raspbian-jessie-lite.img and see what happens... |
|
Ahh... no joy on fresh install either... |
|
ok. different error at least. I think the error you are seeing was something that was fixed. Are you using the "master" branch or "dev" ? |
|
I'd done a |
|
can you pls give a little more context: what was the last action / input from you before the installer crashed? I don't have a fresh pi at hand, but I'll see what I can do - perhaps I can set aside a little time on the weekend if we can't get it working this way. |
|
can you pls provide a |
|
Sure: I'll try another fresh build with Raspbian Jessie Lite and see how that goes. |
|
ok... pls state what happened last before it breaks, thanks and pls leave the hostname as the default, just for the sake of testing, tnx |
|
just reinstalled from scratch, and didn't run into this issue. |
|
Before the blowup, had just answered dialog with the confirm/caution about the port/subnet being exempted from monitoring on 2222 by pressing enter on keyboard. I'll leave the hostname alone this pass.. just going to do: sudo raspi-config sudo apt-get update sudo apt-get install git cd dshield and record what happens |
|
Result: I don't know if this makes a difference but this is a Raspberry Pi 3 not a 2B. |
|
I have it running also on a 3 ... Can you pls state what your choices were and where it broke? I'll add more logging if I can find the time. |
|
The only choice presented by the install.sh was the "do you want to convert to a honeypot" dialog, and I pressed 'enter' to select Yes. The script died without presenting any other dialogs. |
|
I ran in several strange python issue with the most recent jessie. To iron out this stuff it will take time. Could you pls try 2017-03-02-raspbian-jessie-lite ? Thanks. |
|
I downloaded 2017-03-02-raspbian-jessie-lite.img from download.raspberrypi.org archive, flashed a 8GB SDHC disk and performed the above commands. Here's the output from the sudo bin/install.sh run: |
|
OK, too bad, the python dependencies are now also occurring in the older distro. Crap. I have to sort that out and unfortunately this will take time. To re-install the honeypot I'd suggest commenting out the cowrie installation stuff from install.sh so that the dshield-stuff gets installed. |
|
Fortunately, my working system is still alive/online and reporting, just not for SSH (no cowrie). |
|
With the 2016-02-09-raspbian-jessie-lite, all went well until the crypto install, then abort. |
|
Hi, I did some extensive changes in the install.sh Can you pls try the following pre-alpha-don't-use-if-you-are-not-totally-crazy version on a clean Raspbian and report back?
Please don't expose the Pi to the Internet, it's only for testing if the installation works now. Don't use for production. Thanks! |
|
Ok.. the Pi is NOT exposed to the internet while I'm doing rebuilds on a test Pi. sudo raspi-config (PW, filesystem expand) sudo apt-get update sudo apt-get install git git clone https://github.com/DShield-ISC/dshield.git So.. the script completed (Yea!). I rebooted and see that cowrie is running as a process and there's a listen on port 2222. |
|
thanks, that's good news... Thanks. Will try to finalize the script for testing today. |
|
and you may also have a look into the installation log if there's any error, thanks |
|
OK, I did some initial testing and created a pull request: |
|
I'm doing a fresh build using 2017-04-10-raspbian-jessie-lite.img as the base build, and a fresh pull from the master dist now that the script has been pulled into master. Build completed ok. I've shutdown the original Pi honeypot and booted with the new system. All appears well.. I'll report back after a few hours with what's been collected. so far (at startup) Last Web Log Received: |
|
Hi, thanks for the good news ... BTW: I also tried an install on a Pi B+ - it worked well, but took about 2h because of compiling the Python stuff. It you can spare the time and the old honeypot: would you mind trying the "brutal" automatic update procedure mentioned in the README.md? |
|
Success! Last Web Log Received: Looks like the new install.sh script does the job! Thanks gebhard73!! I've got a Pi B+ hanging around.. will try it on that and report back. |
|
thanks, glad it worked! |
|
any feedback regarding the B+ or an upgrade of a system installed with the old script? Thanks. |
|
I tried the upgrade on the old B+ using cd dshield Ran, but ended with I'm going to nuke it, and do a full install based on 2017-04-10-raspbian-jessie-lite.img |
|
Here's the ending of the prior old-B+-and-just-update result from the log |
|
Ok, the fresh install was completed successfully on a RPi 2 B+ in about 50 minutes elapsed. Running the bin/install.sh took 40 minutes. Now I have a 'hot standby' for the honeypot :) |
|
Thanks for your help!
Johannes B. Ullrich, Ph.D., Dean of Research, SANS Technology Institute
SANS Security West 2017 (May 9-18) returns to San Diego. Choose from more than 30 hands-on Infosec courses taught by SANS incomparable Instructors plus bonus sessions, Emerging Trends in Cybersecurity discussions, CISO Success Talks, vendor expo, and the challenging Core and DFIR NetWars competitions! Register today! http://www.sans.org <http://www.sans.org/u/qqP>
On 4/26/17, 5:39 PM, "Ken" <notifications@github.com> wrote:
Ok, the fresh install was completed successfully on a RPi 2 B+ in about 50 minutes elapsed. Running the bin/install.sh took 40 minutes. Now I have a 'hot standby' for the honeypot :)
—
You are receiving this because you commented.
Reply to this email directly,
view it on GitHub <#34 (comment)>, or
mute the thread <https://github.com/notifications/unsubscribe-auth/ABjRT2EAXz7nb6W2cGDiut7k85oRLOVYks5rz7megaJpZM4M_l6d>.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/DShield-ISC/dshield","title":"DShield-ISC/dshield","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/DShield-ISC/dshield"}},"updates":{"snippets":[{"icon":"PERSON","message":"@ktrue in #34: Ok, the fresh install was completed successfully on a RPi 2 B+ in about 50 minutes elapsed. Running the bin/install.sh took 40 minutes. Now I have a 'hot standby' for the honeypot :)"}],"action":{"name":"View Issue","url":"#34 (comment)"}}}
|
|
Since I've completed two successful fresh builds (one on a RPi 2B+ and one on a RPi 3 which is running the current honeypot), I consider this issue 'fixed' and am closing the comment. |
![https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open](https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open){kind=link}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just did a
cd dshield
git pull
sudo bin/install.sh
with today's update to install.sh on a running HPot system and receive this error:
User cowrie already exists in OS. Making no changes
cowrie mysql database already exists. not touching it.
Adding / updating cowrie user in MySQL. +checking cowrie dependency: module 'twisted' ...
ERR: is installed in v14.0.2 but must at least be v16.6.0, will be updated
Downloading/unpacking twisted==16.6.0
Downloading Twisted-16.6.0.tar.bz2 (3.0MB): 3.0MB downloaded
Running setup.py (path:/tmp/pip-build-5bc9R3/twisted/setup.py) egg_info for package twisted
Traceback (most recent call last):
File "", line 3, in
File "/usr/lib/python2.7/dist-packages/setuptools/command/egg_info.py", line 14, in
from setuptools.command.sdist import sdist
File "/usr/lib/python2.7/dist-packages/setuptools/command/sdist.py", line 9, in
from setuptools import svn_utils
File "/usr/lib/python2.7/dist-packages/setuptools/svn_utils.py", line 12, in
from setuptools.py31compat import TemporaryDirectory
File "/usr/lib/python2.7/dist-packages/setuptools/py31compat.py", line 2, in
import unittest
File "/usr/lib/python2.7/unittest/init.py", line 58, in
from .result import TestResult
ValueError: bad marshal data (unknown type code)
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "", line 3, in
File "/usr/lib/python2.7/dist-packages/setuptools/command/egg_info.py", line 14, in
File "/usr/lib/python2.7/dist-packages/setuptools/command/sdist.py", line 9, in
File "/usr/lib/python2.7/dist-packages/setuptools/svn_utils.py", line 12, in
File "/usr/lib/python2.7/dist-packages/setuptools/py31compat.py", line 2, in
File "/usr/lib/python2.7/unittest/init.py", line 58, in
ValueError: bad marshal data (unknown type code)
Cleaning up...
Command python setup.py egg_info failed with error code 1 in /tmp/pip-build-5bc9R3/twisted
Storing debug log for failure in /root/.pip/pip.log
Error upgrading 'twisted'. Aborting.
The text was updated successfully, but these errors were encountered: