[unison-users] Unison 2.48 failing after linux upgrade

[Roderick Usher [e-mail] [unison-users]]

Hi All,

I use unison between several computers and a linux workstation, on which I
don't have root access. Recently, unison has stopped working. I get
this when I try and run it between an iMac running the lastest version of
OSX, and the linux workstation running Fedora 22.

Fatal error: Received unexpected header from the server:
expected "Unison 2.48\n" but received "\nSorry, a version of this program
does not exist for\nthis operating system/machine/user combination\n\n",
which differs at "\n".
This can happen because you have different versions of Unison
installed on the client and server machines, or because
your connection is failing and somebody is printing an error
message, or because your remote login shell is printing
something itself before starting Unison.

What confuses me is the iMac version is

$ unison -version

2017-01-30 17:45:22.768 Unison[14829:2376300] Calling nonGuiStartup

unison version 2.48.3

And in the profile I specifically call /usr/local/bin/unison-2.48.3 on the
workstation. So, the version seems like it should be consistent. I've
ssh'd into the workstation to confirm that there are no network problems.
The only thing that is different is that the workstation was recently
upgraded from Fedora 20 to Fedora 22.

I have tried running unison between an old macbook and the
linux workstation, and I run into similar, but not exact issues, so I infer
there is something wrong on the linux side. I have run unison from the
command line using the debug flag, but it doesn't seem to tell me anything
about why it can't connect.

Can you offer some advice as to how best to proceed? Thanks!

[Roderick Usher [e-mail] [unison-users]]

Quick update. I installed the Ubuntu binary for 2.48.3 locally and have
tried that. Unison now connects okay, but it is far slower than I've ever
seen it before. I then ran it in debug mode and see this. I wonder if
the cache miss is because I am running an older Ubuntu binary on Fedora?
Thanks.

[server: update] buildUpdate -> New file

[server: fpcache] cache miss for path Inactive_Classes / geol12x / geo120 /
geol120_Fall_08 / web_assignments / discharge_figs / exceedence_plot.jpg

[server: xferhint] insertEntry: fspath=/nfs/seismo/Private/derek/Classes,
path=Inactive_Classes/geol12x/geo120/geol120_Fall_08/web_assignments/discharge_figs/exceedence_plot.jpg,
fp=(3adb44efc24ade0f71da4b769cbdc028,)

[server: pred] ignore
'Inactive_Classes/geol12x/geo120/geol120_Fall_08/web_assignments/discharge_figs/exceedence_plot.png'
= false

[server: update] buildUpdateRec:
/nfs/seismo/Private/derek/Classes/Inactive_Classes/geol12x/geo120/geol120_Fall_08/web_assignments/discharge_figs/exceedence_plot.png

[server: update] buildUpdate -> New file

[server: fpcache] cache miss for path Inactive_Classes / geol12x / geo120 /
geol120_Fall_08 / web_assignments / discharge_figs / exceedence_plot.png

[server: xferhint] insertEntry: fspath=/nfs/seismo/Private/derek/Classes,
path=Inactive_Classes/geol12x/geo120/geol120_Fall_08/web_assignments/discharge_figs/exceedence_plot.png,
fp=(8f91e062c91683d25bdbf13e0f2eae2c,)

[server: pred] ignore
'Inactive_Classes/geol12x/geo120/geol120_Fall_08/web_assignments/discharge_figs/exceedence_plot.wmf'
= false

[server: update] buildUpdateRec:
/nfs/seismo/Private/derek/Classes/Inactive_Classes/geol12x/geo120/geol120_Fall_08/web_assignments/discharge_figs/exceedence_plot.wmf

On Mon, Jan 30, 2017 at 5:54 PM, Roderick Usher <

Post by Roderick Usher ***@gmail.com [unison-users]
Hi All,
I use unison between several computers and a linux workstation, on which I
don't have root access. Recently, unison has stopped working. I get
this when I try and run it between an iMac running the lastest version of
OSX, and the linux workstation running Fedora 22.
expected "Unison 2.48\n" but received "\nSorry, a version of this program
does not exist for\nthis operating system/machine/user combination\n\n",
which differs at "\n".
This can happen because you have different versions of Unison
installed on the client and server machines, or because
your connection is failing and somebody is printing an error
message, or because your remote login shell is printing
something itself before starting Unison.
What confuses me is the iMac version is
$ unison -version
2017-01-30 17:45:22.768 Unison[14829:2376300] Calling nonGuiStartup
unison version 2.48.3
And in the profile I specifically call /usr/local/bin/unison-2.48.3 on the
workstation. So, the version seems like it should be consistent. I've
ssh'd into the workstation to confirm that there are no network problems.
The only thing that is different is that the workstation was recently
upgraded from Fedora 20 to Fedora 22.
I have tried running unison between an old macbook and the
linux workstation, and I run into similar, but not exact issues, so I infer
there is something wrong on the linux side. I have run unison from the
command line using the debug flag, but it doesn't seem to tell me anything
about why it can't connect.
Can you offer some advice as to how best to proceed? Thanks!

[Alan Schmitt [e-mail] [unison-users]]

Quick update. I installed the Ubuntu binary for 2.48.3 locally and
have tried that. Unison now connects okay, but it is far slower than
I've ever seen it before. I then ran it in debug mode and see this. I
wonder if the cache miss is because I am running an older Ubuntu
binary on Fedora? Thanks.

Yes, I'm pretty sure that caches are version dependent, so upgrading to
2.48 may require to rebuild the cache.

Best,

Alan

[[e-mail] [unison-users]]

Post by Roderick Usher ***@gmail.com [unison-users]
And in the profile I specifically call /usr/local/bin/unison-2.48.3 on the
workstation. So, the version seems like it should be consistent. I've
ssh'd into the workstation to confirm that there are no network problems.
The only thing that is different is that the workstation was recently
upgraded from Fedora 20 to Fedora 22.

Have you ssh'ed into the workstation and specifically queried
"/usr/local/bin/unison-2.48.3" as to what it reports its verion to be?

The fact that you wrote a bug report containing the phrase "it should be
consistent" should warn you that there are important facts you haven't
verified.

(My suspicion is that at some point the workstation was running 2.48.3
as /usr/local/bin/unison and you set a link from
/usr/local/bin/unison-2.48.3 to /usr/local/bin/unison. And then you
upgraded the workstation.)

Dale