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.

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

Failed to open log file for writing, #10

Open
kolet opened this issue Feb 8, 2017 · 9 comments
Open

Failed to open log file for writing, #10

kolet opened this issue Feb 8, 2017 · 9 comments

Comments

@kolet
Copy link

kolet commented Feb 8, 2017

root@scw-8bceb9:~/down/dnschef# ./dnschef.py -i 10.1.20.92 --fakeip xx.xx.xx.xx --logfile=1 _ _ __ | | version 0.3 | | / _| __| |_ __ ___ ___| |__ ___| |_ / _ | '_ / |/ | ' \ / _ \ |
| (
| | | | _
\ (
| | | | / |
_,|| ||
/_|| ||__|_|
[email protected]

[] DNSChef started on interface: 10.1.20.92
[
] Using the following nameservers: 8.8.8.8
[*] Cooking all A replies to point to xx.xx.xx.xx
[!] Failed to open log file for writing.
`

first time using this python script everything work great. BUT when restarting my server i receive this error

the log file show this [08/Feb/2017:14:01:48 +0000] DNSChef is active.

i tried to remove the dnschef folder and download it from the beging i am receiving the same error.

@7c
Copy link

7c commented Feb 21, 2017

same here, but in my case i throws this exception by first start. version 0.3

@0x4d4c
Copy link

0x4d4c commented Mar 6, 2017

To sort this out: did you check whether there was a different process running on the IP/port combination you tried to start DNSChef on? IIRC the "failed to open log file" error pops up in this case as well.

@kolet
Copy link
Author

kolet commented Mar 9, 2017

actualy i did, i closed all proccess ,checked that no one of the port were taken.
the only thing to make it work is to reset the whole server..

@emirotin
Copy link

This is a gimmick, bad error reporting. What's actually happening is IOError code 13 (permission denied) is thrown on an attempt to bind to the default port 53 which requires the root permissions

@dpicollege
Copy link

i have same error even i start with root? any solution for that?

@pkosmala
Copy link

Same problem here. Nothing's running on port 53, but I get "Failed to open log file for writing".

@GrrrDog
Copy link

GrrrDog commented Jan 25, 2019

In my case, it was systemd-resolved on port 53.
I stopped it and dnschef started working as usual.

https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants
@emirotin @pkosmala @GrrrDog @0x4d4c @kolet @dpicollege @7c and others