Build Issues on Ubuntu

110 views
Skip to first unread message

Chris Hopkins

unread,
Jun 15, 2020, 4:59:21 PM6/15/20
to golang-nuts
Hi,
(Sorry I've not been active in the group for a long time - job change caused other changes!)
I'm seeing a very strange error on building on one of my machines, in fact I'm seeing it on any attempt to build any go project on that machine e.g.

~/home/git/src/github.com/cbehopkins/medorg$ go build check_calc/main.go 
check_calc/main.go:8:2: read /home/xxx/home/git/src/github.com/cbehopkins/medorg/checksum_test.go: read /home/xxx/home/git/src/github.com/cbehopkins/medorg/checksum_test.go: interrupted system call

Builds on other machines work fine, so it's something specific to this one.
Literally a hello world does this. I suspected at first it being linked to how that directory is mounted (it's a samba share), but the same happens on the native file system.
Go versions I've used:
The ubuntu default 1.14.4
14.4 built on a different machine and then copied locally (tricky to do as it requires cross compliation).

The only unique thing aboout this machine, is it is the only one on my network that is both x86 & Linux, other combinations of x86 and OS work fine. Any hints/ideas on how to debug this would be greatly appriciated. (The OS is 
Ubuntu 20.04 LTS) 

Kind Regards

Chris

Kurtis Rader

unread,
Jun 15, 2020, 5:15:26 PM6/15/20
to Chris Hopkins, golang-nuts
Are you perhaps using NFS (or some other network filesystem) and using "soft" mounts with a non-zero timeout? Check the output of "df -T .".

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/c481e6bc-eb38-43f2-9339-18e56db60bc9o%40googlegroups.com.


--
Kurtis Rader
Caretaker of the exceptional canines Junior and Hank

Ian Lance Taylor

unread,
Jun 15, 2020, 5:27:00 PM6/15/20
to Chris Hopkins, golang-nuts
On Mon, Jun 15, 2020 at 1:59 PM Chris Hopkins <cbeho...@gmail.com> wrote:
>
I don't know why this is happening, but you can probably make progress
by setting

GODEBUG=asyncpreemptoff=1

That won't fix the general problem, but it will make it happen less frequently.

Ian

Chris Hopkins

unread,
Jun 16, 2020, 4:12:34 AM6/16/20
to golang-nuts
Yep, the asyncpreempt has definitly made it work.(But for how long Dun Dun Duuuuun!!!)

Humm, interesting. Thanks I can do some more investigation now.


Kind Regards

Chris

Brian Candler

unread,
Jun 16, 2020, 5:33:16 AM6/16/20
to golang-nuts
On Monday, 15 June 2020 21:59:21 UTC+1, Chris Hopkins wrote:

What about the 1.14.4 precompiled binary?

It might be worth looking at the last few pages of strace output just before it crashes:
strace -f go build blah
to see if it gives any clues.

Chris Hopkins

unread,
Jun 16, 2020, 12:39:58 PM6/16/20
to golang-nuts
We have a winner!
Lots of attempts to read /usr/local/go/src/syscall, which is very read only
And not any go install it should be using, looks like GOTOOL was pointing at the wrong place(the default install, not any of the ones I did). No idea who is setting that up, but I can soon fix that.

Thanks!
Reply all
Reply to author
Forward
0 new messages