Gustavo: I'll ask them next time to update snapd through apt and reinstall our snap and see what happens.
Is there a fall back variable we can use for older versions? Or a specific version of snap / snapd we should tell them they need? Thanks, On Fri, Oct 21, 2016, 20:41 Gustavo Niemeyer <[email protected]> wrote: > Hey Aaron, > > The most likely cause is, as you suspected, an out of date snapd. > SNAP_COMMON was introduced some time after 16.04 (don't have exact version > at hand right now). > > With recent versions of snapd, the running infrastructure was > significantly improved and simplified compared to 16.04 pristine, so it > seems less likely to be a problem if up-to-date. > > Please let us know if you find any other hints. > > Gustavo > > On Oct 21, 2016 11:39 AM, "Aaron Ogle" <[email protected]> wrote: > > Didier: > > Like I said its only happened to a few people, never had it personally. > One upgraded to 16.10 and it went away(got impatient 😀 I think). Is there > some piece of information I could get from them that might assist in the > reproduction of the issue? > > On Fri, Oct 21, 2016, 04:19 Didier Roche <[email protected]> wrote: > > Le 20/10/2016 à 17:36, Aaron Ogle a écrit : > > Hey guys, > > > Hey Aaron, > > > With our Rocket.Chat server snap. We've had several cases now where users > come to us trying to figure out why it hasn't started yet after installing. > > Our snap: > https://github.com/RocketChat/Rocket.Chat/blob/develop/.snapcraft/stable/snapcraft.yaml > > rocketchat-mongo: > command: env LC_ALL=C mongod --smallfiles --dbpath=$SNAP_COMMON > > > This is correct, and the generated wrapper (just checked, downloaded it > from the store) is doing: > exec "env" LC_ALL=C mongod --smallfiles --dbpath=$SNAP_COMMON "$@" > > > > After explaining to them how to get logs, it will say our mongo install is > missing the dbpath. > > The exact error they are getting: > Error parsing command line: the argument for option '--dbpath' should > follow immediately after the equal sign > > This seems like for some reason SNAP_COMMON isn't getting set. > > I've confirmed that they are using version 2.15 of snap / snapd. > > I also asked them to drop into the snap: sudo snap run --shell > rocketchat-server > > Then do an: env to see if SNAP_COMMON is even set. From there it does seem > to be set. > > Is it the case as well for you? I just tried this and: > > didrocks@tidus:~$ sudo snap run --shell rocketchat-server > root@tidus:/home/didrocks# env | grep SNAP_COMMON > SNAP_COMMON=/var/snap/rocketchat-server/common > > So, it's set for me, CCing Zyga who might have an idea if there are some > cases where snap-confine doesn't set those variables… > > Cheers, > Didier > -- > Snapcraft mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/snapcraft > > -- > > *Aaron Ogle* Core Developer > > [email protected] > > @aaron.ogle > > https://rocket.chat > > -- > Snapcraft mailing list > [email protected] > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/snapcraft > > -- *Aaron Ogle* Core Developer [email protected] @aaron.ogle <https://demo.rocket.chat/direct/aaron.ogle> https://rocket.chat
-- Snapcraft mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
