public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: [0.9.12] export --format xt_geoip: (25, 'Inappropriate ioctl for device')
Date: Tue, 29 Mar 2022 15:10:54 +0100	[thread overview]
Message-ID: <F89458DE-0F1F-4ED2-829A-CA5B2B50B837@ipfire.org> (raw)
In-Reply-To: <CA+sCei11=+qTjjeWT+D0_8VRJZQhg+mwZn_BGcMmfSxHriKViw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

Hello Valters,

Hmm, this should not happen like this.

I am not even sure why this is trying to do any ioctls for terminals on the output file.

Is this reproducible with any of the other formats, too, or is it only xt_geoip?

-Michael

> On 29 Mar 2022, at 15:07, Valters Jansons <valter.jansons(a)gmail.com> wrote:
> 
> On v0.9.12, I am observing an issue with XTGeoIP exports: the *.iv4 files do not get written.
> 
> The sample command I use to reproduce this on Ubuntu 20.04 is very basic:
> location export --format xt_geoip --directory /usr/share/xt_geoip
> 
> All IPv6 outputs are written successfully, but upon reaching IPv4 it errors with:
> (25, 'Inappropriate ioctl for device')
> 
> A quicker test case is to add argument `--family ipv4` so that IPv6 is hopped over and it tries IPv4 right away.
> 
> With strace, it seems to be:
> openat(AT_FDCWD, "/usr/share/xt_geoip/A1.iv4", O_WRONLY|O_CREAT|O_TRUNC|O_CLOEXEC, 0666) = 4
> fstat(4, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
> ioctl(4, TCGETS, 0x7ffd234c3260)        = -1 ENOTTY (Inappropriate ioctl for device)
> 
> Please let me know if I can provide any further information.
> 
> Best regards,
> Valters Jansons


       reply	other threads:[~2022-03-29 14:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+sCei11=+qTjjeWT+D0_8VRJZQhg+mwZn_BGcMmfSxHriKViw@mail.gmail.com>
2022-03-29 14:10 ` Michael Tremer [this message]
2022-03-29 14:16   ` Valters Jansons
2022-03-29 14:25     ` Valters Jansons
     [not found] <CA+sCei3rpFGm=5QYxP-tsG4bjZL6+NQHG07XG540QGVkng5U4w@mail.gmail.com>
2022-03-29 15:03 ` Michael Tremer
2022-03-30 15:36   ` Michael Tremer
2022-03-30 15:59     ` Valters Jansons
2022-03-30 16:04       ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F89458DE-0F1F-4ED2-829A-CA5B2B50B837@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=location@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox