Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cvs import fails due to configuration problem; (was: npm: Bad system call) #2

Open
umrath opened this issue Aug 7, 2023 · 7 comments
Open

cvs import fails due to configuration problem; (was: npm: Bad system call) #2

umrath opened this issue Aug 7, 2023 · 7 comments

Comments

@umrath
Copy link

umrath commented Aug 7, 2023

Massive amount of
npm[22479]: Bad system call
entries in the log

The installation of Firefish itself went fine.
But more or less right from the beginning I see a massive amount of log entries like this:

Aug 07 17:07:16 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:18 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:20 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:22 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:24 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:26 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:28 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:30 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:32 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:34 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:36 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:38 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:40 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:42 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:44 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:46 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:48 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:50 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:52 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:54 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:56 redacted_host_name npm[22479]: Bad system call
Aug 07 17:07:58 redacted_host_name npm[22479]: Bad system call
Aug 07 17:08:00 redacted_host_name npm[22479]: Bad system call
Aug 07 17:08:02 redacted_host_name npm[22479]: Bad system call
Aug 07 17:08:04 redacted_host_name npm[22479]: Bad system call
Aug 07 17:08:06 redacted_host_name npm[22479]: Bad system call
Aug 07 17:08:08 redacted_host_name npm[22479]: Bad system call
Aug 07 17:08:10 redacted_host_name npm[22479]: Bad system call
Aug 07 17:08:12 redacted_host_name npm[22479]: Bad system call
Aug 07 17:08:14 redacted_host_name npm[22479]: Bad system call
Aug 07 17:08:16 redacted_host_name npm[22479]: Bad system call
Aug 07 17:08:18 redacted_host_name npm[22479]: Bad system call
Aug 07 17:08:20 redacted_host_name npm[22479]: Bad system call

Context

I'm running the latest Yunohost stable (11.2.3) on Proxmox 8.0.4.
What's noteworthy, is that the import of contacts from my Mastodon account is not working. I do not see any dedicated error message. But it might be possible that those error message are related.

Steps to reproduce

  1. Install Firefish
  2. create account
  3. follow accounts on the Fediverse (Mastodon, Friendica, Pixelfed)
  4. Import Following-file exported from Mastodon

Expected behavior

I would expect the import to work (worked fine on the latest Calckey-release, not via Yunohost, though).
I would expect not to drown in error messages.

Logs

Potentially related log entries:

Aug 07 17:07:13 redacted_host_name npm[22514]: INFO 1 [drive register] {"size":35710,"md5":"e9cc05fe85f9cab0a13d4ced97c>
Aug 07 17:07:14 redacted_host_name npm[22514]: DONE 1 [drive register] drive file has been created 9i4kltizx6r4rcu7
Aug 07 17:07:14 redacted_host_name npm[22514]: INFO 1 [queue import-following] Importing following of 9i4fq3kqpbvbk8xe >
Aug 07 17:07:14 redacted_host_name npm[22514]: INFO 1 [download-text-file] Temp file is /tmp/tmp-22514-Zg1ARbB0NHRJ
Aug 07 17:07:14 redacted_host_name npm[22514]: INFO 1 [download] Downloading https://redacted_host_name/files/c0d1b3aa->
Aug 07 17:07:14 redacted_host_name npm[22514]: WARN 1 [download] Blocked address: 127.0.0.1
Aug 07 17:07:14 redacted_host_name npm[22514]: Error [ERR_STREAM_PREMATURE_CLOSE]: Premature close
Aug 07 17:07:14 redacted_host_name npm[22514]: at new NodeError (node:internal/errors:405:5)
Aug 07 17:07:14 redacted_host_name npm[22514]: at Request.onclose (node:internal/streams/end-of-stream:154:30)
Aug 07 17:07:14 redacted_host_name npm[22514]: at Request.emit (node:events:526:35)
Aug 07 17:07:14 redacted_host_name npm[22514]: at Request.emit (node:domain:489:12)
Aug 07 17:07:14 redacted_host_name npm[22514]: at emitCloseNT (node:internal/streams/destroy:132:10)
Aug 07 17:07:14 redacted_host_name npm[22514]: at process.processTicksAndRejections (node:internal/process/task_queues:81:21) {
Aug 07 17:07:14 redacted_host_name npm[22514]: code: 'ERR_STREAM_PREMATURE_CLOSE'
Aug 07 17:07:14 redacted_host_name npm[22514]: }
@umrath
Copy link
Author

umrath commented Aug 7, 2023

addendum:

The error at the end is reproducably happening whenever I import a csv-File of exported Mastodon accounts I follow.
Even splitting the file in smaller chunks (100 lines each) does not change the output.

The npm errors are seamingly unrelated, though.

@MatKlein
Copy link

MatKlein commented Aug 9, 2023

Same issue with my installation. None of the import possibilities are functional.

LOGFILE: journalctl
-- Journal begins at Sat 2023-08-05 18:11:03 CEST, ends at Wed 2023-08-09 15:35:39 CEST. --
Aug 09 15:34:05 npm[1631]: Bad system call
Aug 09 15:34:07 npm[1631]: Bad system call
Aug 09 15:34:09 npm[1631]: Bad system call
Aug 09 15:34:11 npm[1631]: Bad system call
Aug 09 15:34:13 npm[1631]: Bad system call
Aug 09 15:34:15 npm[1631]: Bad system call
Aug 09 15:34:17 npm[1631]: Bad system call
Aug 09 15:34:19 npm[1631]: Bad system call
Aug 09 15:34:21 npm[1631]: Bad system call
Aug 09 15:34:23 npm[1631]: Bad system call
Aug 09 15:34:25 npm[1631]: Bad system call
Aug 09 15:34:27 npm[1631]: Bad system call
Aug 09 15:34:29 npm[1631]: Bad system call
Aug 09 15:34:31 npm[1631]: Bad system call
Aug 09 15:34:33 npm[1631]: Bad system call
Aug 09 15:34:35 npm[1631]: Bad system call
Aug 09 15:34:37 npm[1631]: Bad system call
Aug 09 15:34:39 npm[1631]: Bad system call
Aug 09 15:34:41 npm[1631]: Bad system call
Aug 09 15:34:43 npm[1631]: Bad system call
Aug 09 15:34:45 npm[1631]: Bad system call
Aug 09 15:34:47 npm[1631]: Bad system call
Aug 09 15:34:49 npm[1631]: Bad system call
Aug 09 15:34:51 npm[1631]: Bad system call
Aug 09 15:34:53 npm[1631]: Bad system call
Aug 09 15:34:55 npm[1631]: Bad system call
Aug 09 15:34:57 npm[1631]: Bad system call
Aug 09 15:34:59 npm[1631]: Bad system call
Aug 09 15:35:00 npm[1712]: INFO 1        [queue check-expired-mutings]        Checking expired mutings...
Aug 09 15:35:00 npm[1712]: DONE 1        [queue check-expired-mutings]        All expired mutings checked.
Aug 09 15:35:01 npm[1631]: Bad system call
Aug 09 15:35:03 npm[1631]: Bad system call
Aug 09 15:35:05 npm[1631]: Bad system call
Aug 09 15:35:07 npm[1631]: Bad system call
Aug 09 15:35:09 npm[1631]: Bad system call
Aug 09 15:35:11 npm[1631]: Bad system call
Aug 09 15:35:13 npm[1631]: Bad system call
Aug 09 15:35:15 npm[1631]: Bad system call
Aug 09 15:35:17 npm[1631]: Bad system call
Aug 09 15:35:19 npm[1631]: Bad system call
Aug 09 15:35:21 npm[1631]: Bad system call
Aug 09 15:35:23 npm[1631]: Bad system call
Aug 09 15:35:25 npm[1631]: Bad system call
Aug 09 15:35:27 npm[1631]: Bad system call
Aug 09 15:35:29 npm[1631]: Bad system call
Aug 09 15:35:31 npm[1631]: Bad system call
Aug 09 15:35:33 npm[1631]: Bad system call
Aug 09 15:35:35 npm[1631]: Bad system call
Aug 09 15:35:37 npm[1631]: Bad system call
Aug 09 15:35:39 npm[1631]: Bad system call

@Zeitverschreib
Copy link

I have the same situation regarding Bad system call, but that was already the case with Calckey_ynh. So far both instances are running just fine.

Import problem: please check your default.yml under .config. There's a section for allowedPrivateNetworks. Remove the # and restart the service. That should do the trick.

@MatKlein
Copy link

Import problem: please check your default.yml under .config. There's a section for allowedPrivateNetworks. Remove the # and restart the service. That should do the trick.

Yes, that did the trick. Thanks a lot. I've been runnnig to the file more than hundred times, but not realized the connection. Once again, thanks a lot.

@lapineige
Copy link
Member

lapineige commented Aug 11, 2023 •
edited
Loading

So this references two issues : the bad system call (that you can ignore) + the CSV important issue, that should be documented / fixed.

Can you change the title @umrath to reflects this, or could @Zeitverschreib open a new issue to document that fix ? 🙏

@umrath umrath changed the title npm: Bad system call cvs import fails due to configuration problem; (was: npm: Bad system call) Aug 11, 2023
oufmilo referenced this issue Aug 15, 2023
@oufmilo
Fix bad system call
0f8d8a1
@Happyfeet01
Copy link

I have the same situation regarding Bad system call, but that was already the case with Calckey_ynh. So far both instances are running just fine.

Import problem: please check your default.yml under .config. There's a section for allowedPrivateNetworks. Remove the # and restart the service. That should do the trick.

That was the solution. :-)

@lapineige
Copy link
Member

@oufmilo do you know what that line is supposed to do ?
Could we simply remove it ?

This was referenced Mar 31, 2024
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update config and allow localhost laozhoubuluo/firefish_ynh
5 participants
@umrath @Happyfeet01 @lapineige @Zeitverschreib @MatKlein