No log files found in the logging directory of docker container running on Apple M1

[subhod-i]

Describe the bug
While debugging on why node fails to start up, wanted to have a look at the debug logs but the /home/aeternity/node/log directory is empty.

To Reproduce

1. Set the logging to debug

logging:
    # Controls the overload protection in the logs.
    hwm: 50
    # Sets the level of logging.
    level: debug

2. docker-compose up -d
3. docker exec -it *** bash
4. ls log

Expected behavior
Logging directory with different logging files

Please tell us about your environment:

• docker version : v20.10.10
• docker-compose verison: v2.1.1
• branch: develop
• OS: M1 Pro Apple Silicon running docker on rosetta 2

[marc0olo]

not sure if there is a problem. but I guess the js-sdk repo is the wrong place to discuss that

[subhod-i]

I am using the docker-compose files from this repo so that if someones encounter this while working on SDK can also refer to this issue. The Major problem is that why Node fails to start but to submit that issue I need more logs.

[marc0olo]

I see you have an Apple M1. I guess this is the problem. we aren't compatible right now. see aeternity/aeternity#3632 - as far as I know this is being addressed by the foundation in the near future

[davidyuk]

I've enabled logging as in the example above in docker/aeternity_node_mean16.yaml, executed docker-compose up
and I see much more debug output, like:

aepp-sdk-js-node-1      | 07:57:43.207 [debug] Worker <0.2670.0> created

also, I found logs in log folder of container:

$ docker exec -it aepp-sdk-js-node-1 bash
aeternity@node:~/node$ ls -lah log/*
-rw-r--r-- 1 aeternity aeternity    0 Nov 23 07:51 log/aestratum.log
-rw-r--r-- 1 aeternity aeternity 882K Nov 23 07:58 log/aeternity.log
-rw-r--r-- 1 aeternity aeternity 665K Nov 23 07:58 log/aeternity_metrics.log
-rw-r--r-- 1 aeternity aeternity 1.1M Nov 23 07:58 log/aeternity_mining.log
-rw-r--r-- 1 aeternity aeternity 4.1M Nov 23 07:58 log/aeternity_mining.log.0
-rw-r--r-- 1 aeternity aeternity 4.1M Nov 23 07:57 log/aeternity_mining.log.1
-rw-r--r-- 1 aeternity aeternity 4.1M Nov 23 07:55 log/aeternity_mining.log.2
-rw-r--r-- 1 aeternity aeternity 1.7M Nov 23 07:58 log/aeternity_pow_cuckoo.log
-rw-r--r-- 1 aeternity aeternity 4.1M Nov 23 07:58 log/aeternity_pow_cuckoo.log.0
-rw-r--r-- 1 aeternity aeternity 4.2M Nov 23 07:57 log/aeternity_pow_cuckoo.log.1
-rw-r--r-- 1 aeternity aeternity 4.1M Nov 23 07:55 log/aeternity_pow_cuckoo.log.2
-rw-r--r-- 1 aeternity aeternity  212 Nov 23 07:57 log/aeternity_sync.log
-rw-r--r-- 1 aeternity aeternity    0 Nov 23 07:51 log/crash.log

So, I can't reproduce this issue on an Intel CPU, I don't think that this logging should be enabled by default

[subhod-i]

It's the same problem even without enabling logging. We know it's failing to run on the M1 chip but sure what the error is. Terminal logs are none and this is where I wanted to look at the logger files. Unfortunately even those are not found. Anyway, the issue has been identified here aeternity/aeternity#3632

[davidyuk]

Let's reopen this after the upstream issue will be solved and if we have something not working after that.