Skip to content
This repository has been archived by the owner on Aug 21, 2023. It is now read-only.

Automated Install Script Fails #14

Open
mememememememe opened this issue Jul 17, 2013 · 10 comments
Open

Automated Install Script Fails #14

mememememememe opened this issue Jul 17, 2013 · 10 comments

Comments

@mememememememe
Copy link

I created a brand new raspian install on a 4-gig SD card, expanded the filesystem, and ran the curl -s http://byzantium.github.io/ByzPi/install.sh | bash command to perform the 'effortless' and 'automated' install of ByzPi:

Installing the ByzPi puppet module.
Applying the ByzPi configuration.
Failed to parse template /home/pi/ByzPi/puppet-etc/modules/byzpi/templates/etc/stunnel:
Filepath: /usr/lib/ruby/vendor_ruby/puppet/parser/templatewrapper.rb
Line: 84
Detail: Is a directory - /home/pi/ByzPi/puppet-etc/modules/byzpi/templates/etc/stunnel
at /etc/puppet/modules/byzpi/manifests/init.pp:44 on node meshpi.foo.bar
Applying the byzpi configuration failed.

Nice work on hitting the milestone :)

@Sitwon
Copy link
Member

Sitwon commented Jul 17, 2013

Sorry about that! Last night Doc and I were up late working on updating
ByzPi with the latest and greatest features that were added to Byzantium.
We left it in a half-finished state last night, but we will be finishing
and cleaning it up tonight. Please bear with us.

Thanks,
Ben the Pyrate

On Wed, Jul 17, 2013 at 2:06 PM, mememememememe [email protected]:

I created a brand new raspian install on a 4-gig SD card, expanded the
filesystem, and ran the curl -s
http://byzantium.github.io/ByzPi/install.sh | bash command to perform the
'effortless' and 'automated' install of ByzPi:

Installing the ByzPi puppet module.
Applying the ByzPi configuration.
Failed to parse template
/home/pi/ByzPi/puppet-etc/modules/byzpi/templates/etc/stunnel:
Filepath: /usr/lib/ruby/vendor_ruby/puppet/parser/templatewrapper.rb
Line: 84
Detail: Is a directory -
/home/pi/ByzPi/puppet-etc/modules/byzpi/templates/etc/stunnel
at /etc/puppet/modules/byzpi/manifests/init.pp:44 on node meshpi.foo.bar
Applying the byzpi configuration failed.

Nice work on hitting the milestone :)


Reply to this email directly or view it on GitHubhttps://github.com//issues/14
.

@mememememememe
Copy link
Author

Ah cool! I'd manually gone through the script to correct the file references but then ended up with a load of

notice: /Stage[main]/Byzpi::Packages/Exec[apt-get -q update]/returns: executed successfully
notice: /Stage[main]/Byzpi::Packages::Apt/Package[ax25-xtools]/ensure: ensure changed 'purged' to 'present'
notice: /Stage[main]/Byzpi::Packages::Apt/Package[openssl-blacklist]/ensure: ensure changed 'purged' to 'present'

notice: /Stage[main]/Byzpi::Packages::Apt/Package[python-pip]/ensure: ensure changed 'purged' to 'present'
notice: /Stage[main]/Byzpi::Packages::Apt/Package[olsrd]/ensure: ensure changed 'purged' to 'present'

I'll leave it with you. Great project btw.

@karticbhargav
Copy link

Hello,
I just came across this thread now after an extensive search since I too have been facing a similar problem although I don't think its because of an installation failure. So after installing the ByzPi from the install script, its just the RaspBian desktop that boots up again. No sign of Byzantium at all, except for a ByzPi folder under root.

I guess it could be a problem with my Wi-Fi dongle. I use an Asus N10 - Maybe its not supported by the kernel as of yet. (Not listed here http://bit.ly/175uhO3)

And what's more, this Wifi dongle that was working prior to the ByzPi installation is not working now on the Pi (I used it for the complete installation process and on reboot it failed to work normally) :/ . Probably the reconfiguration of the kernel has caused this too. So can't connect wirelessly to the network as well :/. Any leads of how I could detect the exact source of the problem and how to resolve it?

Thanks,
Kartic

@Sitwon
Copy link
Member

Sitwon commented Oct 4, 2013

Wow, I'm not sure how we missed that. the Asus N10 is not supported at all with Byzantium. We actually have two which we've tested and found that the current drivers do not properly support IBSS (ad-hoc mode). Specifically, you cannot set the BSSID/Cell address correctly so it's useless if you're the first node in the network.

It was documented here (bottom of the page): https://github.com/Byzantium/Byzantium/wiki/HCL
I'm not sure why we have two separate pages for essentially the same information.

@haxwithaxe
Copy link
Contributor

can you run
curl -s http://byzantium.github.io/ByzPi/install.sh | bash 2>&1 | tee /tmp/byzpi-install.log
and post as an attatchment here please?

@karticbhargav
Copy link

Hello,
I did run : curl -s http://byzantium.github.io/ByzPi/install.sh | bash 2>&1 | tee /tmp/byzpi-install.log.

I did this after a fresh installation. I am attaching the result below.
Thanks a lot. :)

PS: Kindly ignore my latest post on the Byz Google Group. I had almost forgotten that I had filed a ticket here!

install-log

@karticbhargav
Copy link

Hello,
For your reference, I ran the same command again on a Fresh Image of the Raspbian Wheezy. I am attaching the file. In case not accessible, Please download from this link : http://bit.ly/1c0iDg8 .

Thanks,

On Tuesday, 15 October 2013 9:15 PM, haxwithaxe [email protected] wrote:

can you run
curl -s http://byzantium.github.io/ByzPi/install.sh | bash 2>&1 | tee /tmp/byzpi-install.log
and post as an attatchment here please?

Reply to this email directly or view it on GitHub.

@virtadpt
Copy link
Member

haxwithaxe created a bugfix branch in response to ticket #16. I've added some code to address this in commit a05758a. I think that'll fix the problem that you're seeing.

@Sitwon
Copy link
Member

Sitwon commented Jan 21, 2014

Is this resolved?

@virtadpt
Copy link
Member

Haven't tried it yet. I'll give it a shot when I get home from work tonight.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants