Console-conf and ip address

[Julia Palandri]

Ahá! Apparently the rpi2 image doesn't deliver snapweb :) (snap list
doesn't show it).

I installed it manually, and now I can access it with that name. Thanks!!

On Wed, Oct 5, 2016 at 12:09 AM, Loïc Minier <loic.minier at ubuntu.com> wrote:

> Verify you have latest snapweb, snap list / snap refresh?
>
> You can try restarting snapweb with sudo systemctl restart snap.snapweb.snapweb,
> but that shouldn't be needed after boot
>
> - Loïc
>
> On Tue, Oct 4, 2016 at 8:02 PM, Julia Palandri <
> julia.palandri at canonical.com> wrote:
>
>> Hi,
>>
>> On Tue, Oct 4, 2016 at 7:28 PM, Loïc Minier <loic.minier at ubuntu.com>
>> wrote:
>>
>>> If you have a local console, you can debug this by checking that your
>>> network is up and then look at snapweb service output (sudo journalctl -u
>>> snap.snapweb.snapweb.service).
>>>
>>>
>> I ssh'ed to the rpi2 with IP (thanks for the nmap trick!), and the
>> command you suggested returned no entries. Should I manually enable it?
>> Thanks!
>>
>>
>>> Cheers,
>>> - Loïc
>>>
>>> On Tue, Oct 4, 2016 at 7:24 PM, Julia Palandri <
>>> julia.palandri at canonical.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> On Fri, Sep 23, 2016 at 2:59 PM, Loïc Minier <loic.minier at ubuntu.com>
>>>> wrote:
>>>>
>>>>> I agree this isn't great; I wanted to mention an old but still working
>>>>> workaround: mDNS. Snapweb should publish a snapweb.local mDNS record on
>>>>> your LAN, so ssh you at snapweb.local should work. Note that this only
>>>>> works for one device at a time, so you want to change the hostname to have
>>>>> e.g. rpi3-xyz.local.
>>>>>
>>>>> I tried this on my rpi2 but it didn't work. Grepping in /etc I
>>>> couldn't find any mention to snapweb.local, could it be that only some
>>>> devices have this enabled?
>>>>
>>>> Thanks,
>>>>
>>>>
>>>>> On Fri, Sep 23, 2016 at 11:45 AM, Victor Palau <
>>>>> victor.palau at canonical.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have an issue, and talking to a few people they had it too, where I
>>>>>> set up my user link to my sso via console -conf and failed to write down
>>>>>> the ip address of the box.
>>>>>>
>>>>>> Even having a keyboard and screen connected to the device (RPI2) does
>>>>>> not help to get access to the box, since I never had a chance to set up a
>>>>>> password. So I had to reflash the device and try again.
>>>>>>
>>>>>> My concern is that if I take the device somewhere else or I loose the
>>>>>> lease for that ip and did not set up a password, my only option would be to
>>>>>> reflash the device (if I dont have admin access in the network router i am
>>>>>> connected). This seems a bad user experience.
>>>>>>
>>>>>> Could we not at least have the ip address for the device always
>>>>>> displayed on the console login prompt.
>>>>>>
>>>>>> However, it still feels very fragile user experience
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Victor
>>>>>>
>>>>>> --
>>>>>> Devices mailing list
>>>>>> Devices at lists.snapcraft.io
>>>>>> Modify settings or unsubscribe at: https://lists.snapcraft.io/mai
>>>>>> lman/listinfo/devices
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> - Loïc
>>>>>
>>>>> --
>>>>> Devices mailing list
>>>>> Devices at lists.snapcraft.io
>>>>> Modify settings or unsubscribe at: https://lists.snapcraft.io/mai
>>>>> lman/listinfo/devices
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Julia
>>>>
>>>
>>>
>>>
>>> --
>>> - Loïc
>>>
>>
>>
>>
>> --
>>
>> Julia
>>
>
>
>
> --
> - Loïc
>



-- 

Julia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.snapcraft.io/archives/devices/attachments/20161005/59c3cbf8/attachment.html>