I'm getting an error that the Procfile or Procfile.dev doesn't exist, when both clearly do.
~/Documents/shortstack_apps/shortstackapi(staging*)
» ds start dylanconlin@dylanconlin
docker-sync ✔
mysqldb ✔
docker.elastic.co ✔
Starting shortstackapi_redis_1 ... done
Starting ss-api ... done
Attaching to shortstackapi_redis_1, ss-api
redis_1 | 1:C 19 Nov 2019 18:34:28.477 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 19 Nov 2019 18:34:28.477 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 19 Nov 2019 18:34:28.477 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | 1:M 19 Nov 2019 18:34:28.479 * Running mode=standalone, port=6379.
redis_1 | 1:M 19 Nov 2019 18:34:28.479 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1 | 1:M 19 Nov 2019 18:34:28.479 # Server initialized
redis_1 | 1:M 19 Nov 2019 18:34:28.479 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1 | 1:M 19 Nov 2019 18:34:28.479 * DB loaded from disk: 0.000 seconds
redis_1 | 1:M 19 Nov 2019 18:34:28.479 * Ready to accept connections
ss-api | ERROR: Procfile does not exist.
ss-api exited with code 1I was wondering if it was a problem with docker-sync, so I tried starting docker-sync by itself and got the following:
~/Documents/shortstack_apps/shortstackapi(staging*)
» docker-sync start dylanconlin@dylanconlin
ok Starting unison for sync shortstackapi-sync
ok shortstackapi-sync container still running, restarting unison in container
command docker exec shortstackapi-sync supervisorctl restart unison
ok starting initial sync of shortstackapi-sync
command docker inspect --format='{{(index (index .NetworkSettings.Ports "5000/tcp") 0).HostPort}}' shortstackapi-sync
command unison -testserver /app_sync "socket://127.0.0.1:32774"
command docker inspect --format='{{(index (index .NetworkSettings.Ports "5000/tcp") 0).HostPort}}' shortstackapi-sync
command unison '/Users/dylanconlin/Documents/shortstack_apps/shortstackapi/' -auto -batch -prefer '/Users/dylanconlin/Documents/shortstack_apps/shortstackapi/' -copyonconflict socket://127.0.0.1:32774
error Error starting sync, exit code 0
message Warning: No archive files were found for these roots, whose canonical names are:
/Users/dylanconlin/Documents/shortstack_apps/shortstackapi
//d4f60dc1ebee//app_sync
This can happen either
because this is the first time you have synchronized these roots,
or because you have upgraded Unison to a new version with a different
archive format.
Update detection may take a while on this run if the replicas are
large.
Unison will assume that the 'last synchronized state' of both replicas
was completely empty. This means that any files that are different
will be reported as conflicts, and any files that exist only on one
replica will be judged as new and propagated to the other replica.
If the two replicas are identical, then no changes will be reported.
If you see this message repeatedly, it may be because one of your machines
is getting its address from DHCP, which is causing its host name to change
between synchronizations. See the documentation for the UNISONLOCALHOSTNAME
environment variable for advice on how to correct this.
Donations to the Unison project are gratefully accepted:
http://www.cis.upenn.edu/~bcpierce/unison
message Unison 2.51.2 (ocaml 4.06.1): Contacting server...
Connected [//d4f60dc1ebee//app_sync -> //dylanconlin//Users/dylanconlin/Documents/shortstack_apps/shortstackapi]
Looking for changes
Waiting for changes from server
Fatal error: Fatal error during unmarshaling (input_value: ill-formed message),
possibly because client and server have been compiled with differentversions of the OCaml compiler.
success Unison server started
command docker inspect --format='{{(index (index .NetworkSettings.Ports "5000/tcp") 0).HostPort}}' shortstackapi-sync
command unison '/Users/dylanconlin/Documents/shortstack_apps/shortstackapi/' -auto -batch -prefer '/Users/dylanconlin/Documents/shortstack_apps/shortstackapi/' -copyonconflict socket://127.0.0.1:32774
error Error starting sync, exit code 0
message Warning: No archive files were found for these roots, whose canonical names are:
/Users/dylanconlin/Documents/shortstack_apps/shortstackapi
//d4f60dc1ebee//app_sync
This can happen either
because this is the first time you have synchronized these roots,
or because you have upgraded Unison to a new version with a different
archive format.
Update detection may take a while on this run if the replicas are
large.
Unison will assume that the 'last synchronized state' of both replicas
was completely empty. This means that any files that are different
will be reported as conflicts, and any files that exist only on one
replica will be judged as new and propagated to the other replica.
If the two replicas are identical, then no changes will be reported.
If you see this message repeatedly, it may be because one of your machines
is getting its address from DHCP, which is causing its host name to change
between synchronizations. See the documentation for the UNISONLOCALHOSTNAME
environment variable for advice on how to correct this.
Donations to the Unison project are gratefully accepted:
http://www.cis.upenn.edu/~bcpierce/unison
message Unison 2.51.2 (ocaml 4.06.1): Contacting server...
Connected [//d4f60dc1ebee//app_sync -> //dylanconlin//Users/dylanconlin/Documents/shortstack_apps/shortstackapi]
Looking for changes
Waiting for changes from server
Fatal error: Fatal error during unmarshaling (input_value: ill-formed message),
possibly because client and server have been compiled with differentversions of the OCaml compiler.
success Starting Docker-Sync in the background
I noticed this error in the output above:
message Unison 2.51.2 (ocaml 4.06.1): Contacting server...
Connected [//d4f60dc1ebee//app_sync -> //dylanconlin//Users/dylanconlin/Documents/shortstack_apps/shortstackapi]
Looking for changes
Waiting for changes from server
Fatal error: Fatal error during unmarshaling (input_value: ill-formed message),
possibly because client and server have been compiled with differentversions of the OCaml compiler.
success Starting Docker-Sync in the background
-
I found this github issue related to the issue above: EugenMayer/docker-sync#687. I'm wondering if I should try switching to native_osx from unison?