faas-cli logs not showing anything about faasd

[alexellis]

Hi, thanks for your interest in faasd.

I can't reproduce this issue and am not sure what you may be doing differently. Since faasd is not actually broken, I'm not sure what to do about this issue.

ubuntu@faasd:~$ sudo cat /var/lib/faasd/secrets/basic-auth-password | faas-cli login -u admin -s 
Calling the OpenFaaS server to validate the credentials...
credentials saved for admin http://127.0.0.1:8080
ubuntu@faasd:~$ faas-cli list
Function                      	Invocations    	Replicas
ubuntu@faasd:~$ faas-cli store deploy nodeinfo

Deployed. 200 OK.
URL: http://127.0.0.1:8080/function/nodeinfo

ubuntu@faasd:~$ faas-cli describe nodeinfo
Name:               nodeinfo
Status:             Ready
Replicas:           1
Available Replicas: 1
Invocations:        0
Image:              ghcr.io/openfaas/nodeinfo:latest
Function Process:   node index.js
URL:                http://127.0.0.1:8080/function/nodeinfo
Async URL:          http://127.0.0.1:8080/async-function/nodeinfo
Environment:
 NODE_VERSION: 14.21.1
 NPM_CONFIG_LOGLEVEL: warn
 YARN_VERSION: 1.22.19
 cgi_headers: true
 exec_timeout: 10s
 mode: http
 prefix_logs: false
 read_timeout: 15s
 upstream_url: http://127.0.0.1:3000
 write_timeout: 15s
ubuntu@faasd:~$ curl -i http://127.0.0.1:8080/function/nodeinfo 
HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 91
Content-Type: text/plain; charset=utf-8
Date: Wed, 21 Dec 2022 20:52:54 GMT
Etag: W/"5b-yHDTfrw93ZBV4volbBLAVBDzZ/0"
Keep-Alive: timeout=5
X-Call-Id: 71acacdb-a228-4cc3-9e9b-2b8dd40f521e
X-Duration-Seconds: 0.014444
X-Start-Time: 1671655973991767849

Hostname: localhost

Arch: x64
CPUs: 1
Total mem: 969MB
Platform: linux
Uptime: 1407206.12
ubuntu@faasd:~$ curl -d "verbose" http://127.0.0.1:8080/async-function/nodeinfo 
ubuntu@faasd:~$ faas-cli logs nodeinfo
2022-12-21T20:52:45Z 2022/12/21 20:52:45 Version: 0.9.10	SHA: eefeb9dd8c979398a46fc0decc3297591362bfab
2022-12-21T20:52:45Z 2022/12/21 20:52:45 Forking: node, arguments: [index.js]
2022-12-21T20:52:45Z 2022/12/21 20:52:45 Started logging: stderr from function.
2022-12-21T20:52:45Z 2022/12/21 20:52:45 Started logging: stdout from function.
2022-12-21T20:52:45Z 2022/12/21 20:52:45 Watchdog mode: http	fprocess: "node index.js"
2022-12-21T20:52:45Z 2022/12/21 20:52:45 Timeouts: read: 15s write: 15s hard: 10s health: 15s
2022-12-21T20:52:45Z 2022/12/21 20:52:45 Listening on port: 8080
2022-12-21T20:52:45Z 2022/12/21 20:52:45 Writing lock-file to: /tmp/.lock
2022-12-21T20:52:45Z 2022/12/21 20:52:45 Metrics listening on port: 8081
2022-12-21T20:52:45Z node14 listening on port: 3000
2022-12-21T20:52:54Z 2022/12/21 20:52:54 GET / - 200 OK - ContentLength: 91B (0.0144s)
2022-12-21T20:53:02Z 2022/12/21 20:53:02 POST / - 200 OK - ContentLength: 91B (0.0113s)

Sometimes people may have a conflict with "localhost" and IPv6, so make sure you are using 127.0.0.1:8080 to force IPv4 faas-cli logs nodeinfo -g http://127.0.0.1:8080 - you might also want to try --since 1h

I think that if you work through the troubleshooting chapter of the eBook you may figure it out. Check all the commands for journalctl.

Best,

Alex