opensand team mailing list archive

[Jedrzej Gorski <andy.gorski.dev@xxxxxxxxx>]

Hi Didier,

Tha fresh instalation of Ubuntu VM from Monday crashed today (balck screen)
so I had to install it once again. This is what I get on my fresh
installation:

This is only last part of log file. During compilation I tried to avoid
copy procedures as I mention before.

andyg@andyg-laptop:~/opensand-trunk$ sudo cp /tmp/daemon.conf /etc/opensand/
andyg@andyg-laptop:~/opensand-trunk$ sudo service opensand-network start
opensand-network: unrecognized service
andyg@andyg-laptop:~/opensand-trunk$ sudo service opensand-daemon start
opensand-daemon: unrecognized service
andyg@andyg-laptop:~/opensand-trunk$

I'll be gratefull for some suggestions.


I've also notice something what I can call a small bug in installation
manual.

Section:     Build and install module opensand-core
Paragraph: Deploy some other opensand-core configuration files to MANAGER
Line:          sudo chown -R *opensand* /usr/share/opensand/

I think that world opensand which is bold is ok as long this is login
available in a system. During my compilation I had to change it to andyg to
see positive result.

With kind regards,

Andy

2012/9/4 Jedrzej Gorski <andy.gorski.dev@xxxxxxxxx>

> Didier,
>
> As far as I remember I tried $ sudo service opensand-network start as well
> but I don't have access to this log file at the moment. I will reproduce
> this scenario on my laptop with fresh ubuntu 10.04 LTS installation created
> yesterday.
>
> Regards,
> Andy
>
>
> 2012/9/4 Didier Barvaux <didier.barvaux@xxxxxxxxxxxxxxxxxxxx>
>
>> Andy,
>>
>> > My idea for basic test with source code compilation is to reproduce my
>> > first successful test scenario for packages installation - daemon of
>> > a SAT and sand-manager on single VM. According to manual we can
>> > compile daemon through sources and send results of compilation to
>> > certain hosts. In order to obtain this basic test scenario I decide
>> > to perform only those actions which are necessary for compilation (I
>> > avoid those commands in manual which refers to coping files
>> > procedure).
>> >
>> > I manage to perform all steps for daemon compilation with no error
>> > message until I decide to perform following action (it's a command
>> > based on latest installation manual - section "Installation from
>> > sources" - updated 28.08.2012 - but not exactly the same - I couldn't
>> > use ssh to perform this step):
>> >
>> >
>> > powerxp@powerxp-desktop:~$ service opensand-network start
>> >  * Configuring the OpenSAND
>> > network
>> >
>> > debconf: DbDriver "passwords" warning: could not open
>> > /var/cache/debconf/passwords.dat: Permission denied
>> > Configure OpenSAND Daemon:
>> >     Get user configuration
>> >     Write configuration file
>> > /usr/libexec/opensand/write_initialize_config: 181: cannot create
>> > /etc/opensand/daemon.conf: Permission denied
>> >  * failed to configure the OpenSAND network
>> >
>> > [fail]
>> > powerxp@powerxp-desktop:~$
>>
>> You need to be root for such an action. The ssh command uses the root
>> account. If you do this locally, use "sudo".
>>
>> Regards,
>> Didier
>>
>> --
>> Mailing list: https://launchpad.net/~opensand
>> Post to     : opensand@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~opensand
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>