AFS has sysname fallback built in these days. It looks like in the
mosh_project locker both 16.04 and 14.04 are falling back to
amd64_ubuntu1004 (which is a link to amd64_deb60). If you create a
new amd64_ubuntu1604, you could build for it seperately, while letting
the dialups (14.04) continue to fall back. Of course you'd need a
16.04 build machine, so using the static build may be easiest.
neural-implant:~$ lsb_release -r
Release: 16.04
neural-implant:~$ fs sysname
Current sysname list is 'amd64_ubuntu1604' 'i386_ubuntu1604' 'amd64_ubuntu1510'
'i386_ubuntu1510' 'amd64_deb80' 'i386_deb80' 'amd64_ubuntu1404'
'i386_ubuntu1404' 'amd64_deb70' 'i386_deb70' 'amd64_ubuntu1204'
'i386_ubuntu1204' 'amd64_deb60' 'i386_deb60' 'amd64_ubuntu1104'
'i386_ubuntu1104' 'amd64_ubuntu1004' 'i386_ubuntu1004' 'amd64_ubuntu904'
'i386_ubuntu904' 'amd64_deb50' 'i386_deb50' 'amd64_ubuntu804' 'i386_ubuntu804'
'amd64_deb40' 'i386_deb40' 'i386_rhel4'
speaker-for-the-dead:~$ lsb_release -r
Release: 14.04
speaker-for-the-dead:~$ fs sysname
Current sysname list is 'amd64_ubuntu1404' 'i386_ubuntu1404' 'amd64_deb70'
'i386_deb70' 'amd64_ubuntu1204' 'i386_ubuntu1204' 'amd64_deb60' 'i386_deb60'
'amd64_ubuntu1104' 'i386_ubuntu1104' 'amd64_ubuntu1004' 'i386_ubuntu1004'
'amd64_ubuntu904' 'i386_ubuntu904' 'amd64_deb50' 'i386_deb50' 'amd64_ubuntu804'
'i386_ubuntu804' 'amd64_deb40' 'i386_deb40' 'i386_rhel4'
Jonathon
On Fri, 24 Feb 2017, Keith Winstein wrote:
Hello Lizhou,
Sigh, these should probably not be the same sysname, but I guess that ship has
probably sailed. I reverted to a statically-linked binary, but still compiled
on Athena. utempter seems to be still working
on athena.dialup.
-Keith
On Fri, Feb 24, 2017 at 2:23 PM, Lizhou Sha <s...@mit.edu> wrote:
Hi Keith,
I'm observing a regression for my self-deployed Ubuntu 16.04 dialup
with regards to libprotobuf linkage:
$ mosh --ssh="ssh -K" --server="athrun mosh_project mosh-server"
sha.mit.edu -- byobu a -d
/afs/sipb.mit.edu/project/mosh/arch/amd64_deb60/bin/mosh-server.real:
error while loading shared libraries: libprotobuf.so.8: cannot open
shared object file: No such file or directory
Connection to sha.mit.edu closed.
/usr/bin/mosh: Did not find mosh server startup message.
Best,
Lizhou
On Fri, Feb 24, 2017 at 4:39 PM, Keith Winstein <kei...@cs.stanford.edu>
wrote:
> Hello Jonathon,
>
> I deployed a new build of mosh-server for amd64 architectures (compiled
on
> test.dialup) in the mosh_project locker. It seems to be updating utmp
now.
> Please let me know if you see any trouble.
>
> -Keith
>
> On Fri, Feb 24, 2017 at 1:17 PM, Jonathon Weiss <jwe...@mit.edu> wrote:
>>
>> Hi Keith,
>>
>> libutempter-dev is now installed on test.dialup.mit.edu. It should hit
>> the production dialups over the course of next week, but doing your
>> build on test.dialup.mit.edu should be fine. thanks for the help.
>>
>> Jonathon
>>
>>
>>
>> Keith Winstein <kei...@cs.stanford.edu> wrote:
>>
>> > Hello Jonathon,
>> >
>> > I investigated and it's probably my fault -- I'm compiling and
>> > statically
>> > linking on an Ubuntu system that expects it
>> > in /usr/lib/x86_64-linux-gnu/utempter/utempter, and athena.dialup
has it
>> > in /usr/lib/utempter/utempter.
>> >
>> > Could you please install libutempter-dev on the dialups? Then I can
>> > compile
>> > on Athena, and my guess is it will start working again. (Or I can
spin
>> > up a
>> > VM that more closely matches the dialups if necessary.)
>> >
>> > (Anton, this is a bit of a special case as I am the one who is
building
>> > and
>> > installing Mosh at MIT -- we use this to test release candidates.)
>> >
>> > Regards,
>> > Keith
>> >
>> > On Thu, Feb 23, 2017 at 2:50 PM, Jonathon Weiss <jwe...@mit.edu>
wrote:
>> >
>> > >
>> > > Hello all,
>> > >
>> > > Following up on a zephyr conversation I had with Keith and others
>> > > about a week ago, I was wondering why mosh logins don't appear in
the
>> > > output of "who" or "w" on the athena.dialup.mit.edu servers. We
got
>> > > as far as confirming that utempter was setgid utmp:
>> > >
>> > > -rwxr-sr-x 1 root utmp 10104 Oct 5 2012
/usr/lib/utempter/utempter
>> > >
>> > > oh, these files also appear to me ot have reasonable permissions:
>> > >
>> > > -rw-rw-r-- 1 root utmp 190080 Feb 23 17:47 /var/run/utmp
>> > >
>> > > -rw-rw-r-- 1 root utmp 2704128 Feb 23 17:45 /var/log/wtmp
>> > >
>> > > -rw-rw---- 1 root utmp 992640 Feb 23 17:25 /var/log/btmp
>> > >
>> > > Anything you can suggest to check? Anyhting I can do to help
debug?
>> > >
>> > > Jonathon
>> > >
>> > > Jonathon Weiss <jwe...@mit.edu>
>> > > MIT/IS&T/Infrastructure Design & Engineering
>> > > Cloud Platforms (Server Operations)
>> > > _______________________________________________
>> > > mosh-devel mailing list
>> > > mosh-devel@mit.edu
>> > > http://mailman.mit.edu/mailman/listinfo/mosh-devel
>> > >
>> >
>> > ----------------------------------------------------
>> > Alternatives:
>> >
>> > ----------------------------------------------------
>>
>
>
> _______________________________________________
> mosh-devel mailing list
> mosh-devel@mit.edu
> http://mailman.mit.edu/mailman/listinfo/mosh-devel
>
--
Lizhou Sha
Massachusetts Institute of Technology
Department of Physics
_______________________________________________
mosh-devel mailing list
mosh-devel@mit.edu
http://mailman.mit.edu/mailman/listinfo/mosh-devel
