43 ответов в этой теме

[bardo]

Yeah well okay it doesn't matter, that startup thing with service not starting automatically on boot might be due to something broken in my gentoo installation (though I really doubt that, I don't see how that could be broken) , when I start the service manually it works fine. I guess I can test that in my main gentoo installation but I don't know, might do that in the future, not sure. If the problem is the same there then it's for sure something in Dr.Web or it's a Gentoo only thing somehow.

 

As for Spider Gate, maybe it needs more things enabled in the kernel, have no clue.

[dbanschikov]

Yeah well okay it doesn't matter, that startup thing with service not starting automatically on boot might be due to something broken in my gentoo installation (though I really doubt that, I don't see how that could be broken) , when I start the service manually it works fine. I guess I can test that in my main gentoo installation but I don't know, might do that in the future, not sure. If the problem is the same there then it's for sure something in Dr.Web or it's a Gentoo only thing somehow.

 

As for Spider Gate, maybe it needs more things enabled in the kernel, have no clue.

 

I'm still in process of investigation problem with Spider Gate. I'm sure that you just doesn't have all required kernel config options - but I don't want to guess which one exactly. Please be patient. I will request additional information if it required. 

Сообщение было изменено dbanschikov: 04 Ноябрь 2016 - 17:32

[bardo]

Sure, no problem, take your time, there's no rush.

I guess I can compile the kernel with everything enabled but that's just a waste of time, it would just tell us if that's the problem, but I wouldn't use such a kernel so that's not an option.

[dbanschikov]

Sure, no problem, take your time, there's no rush.

I guess I can compile the kernel with everything enabled but that's just a waste of time, it would just tell us if that's the problem, but I wouldn't use such a kernel so that's not an option.

 

Please show output of iptables-save.

[bardo]

 # iptables-save 
# Generated by iptables-save v1.6.0 on Fri Nov  4 18:21:05 2016
*mangle
:PREROUTING ACCEPT [4260:5760596]
:INPUT ACCEPT [4260:5760596]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [3217:224455]
:POSTROUTING ACCEPT [3217:224455]
COMMIT
# Completed on Fri Nov  4 18:21:05 2016
# Generated by iptables-save v1.6.0 on Fri Nov  4 18:21:05 2016
*nat
:PREROUTING ACCEPT [102:12847]
:INPUT ACCEPT [102:12847]
:OUTPUT ACCEPT [37:2322]
:POSTROUTING ACCEPT [37:2322]
COMMIT
# Completed on Fri Nov  4 18:21:05 2016
# Generated by iptables-save v1.6.0 on Fri Nov  4 18:21:05 2016
*filter
:INPUT ACCEPT [4249:5759609]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [3208:223622]
COMMIT
# Completed on Fri Nov  4 18:21:05 2016

[dbanschikov]

 # iptables-save 
# Generated by iptables-save v1.6.0 on Fri Nov  4 18:21:05 2016
*mangle
:PREROUTING ACCEPT [4260:5760596]
:INPUT ACCEPT [4260:5760596]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [3217:224455]
:POSTROUTING ACCEPT [3217:224455]
COMMIT
# Completed on Fri Nov  4 18:21:05 2016
# Generated by iptables-save v1.6.0 on Fri Nov  4 18:21:05 2016
*nat
:PREROUTING ACCEPT [102:12847]
:INPUT ACCEPT [102:12847]
:OUTPUT ACCEPT [37:2322]
:POSTROUTING ACCEPT [37:2322]
COMMIT
# Completed on Fri Nov  4 18:21:05 2016
# Generated by iptables-save v1.6.0 on Fri Nov  4 18:21:05 2016
*filter
:INPUT ACCEPT [4249:5759609]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [3208:223622]
COMMIT
# Completed on Fri Nov  4 18:21:05 2016

This output was produced when drweb-firewall was running? If yes - this is a root of the problem.
Do you have installed iptables binary?

[bardo]

Yes I have iptables installed and that output was produced when drweb-firewall was running.

What is the problem ?

Should I uninstall it ?

[dbanschikov]

Yes I have iptables installed and that output was produced when drweb-firewall was running.
What is the problem ?
Should I uninstall it ?

The problem is that for whatever reason we don't have required rules in firewall tables.
We have to debug interaction of drweb-firewall with iptables.
Download attached strace.conf.gz, ungzip it and:

1. Disable SpIDer Gate through GUI
2. Stop drweb-configd: service drweb-configd stop
3. Put strace.conf into /etc/opt/drweb.com/ldwrap.conf.d/
4. Start drweb-configd: service drweb-configd start
5. Reproduce problem. Enable SpIDer Gate through GUI.
15-20 seconds of work are enough. Be sure to access some network resources at that time.

6. Stop drweb-configd: service drweb-configd stop
7. Remove /etc/opt/drweb.com/ldwrap.conf.d/strace.conf
8. Start drweb-configd: service drweb-configd start
9. Provide /tmp/com.drweb.strace

Прикрепленные файлы:

•  strace.conf.gz   681байт   3 Скачано раз

[bardo]

Step 6 was a problem, service didn't want to shutdown for some reason, it was a long wait until it said that it couldn't shut it down.

Step 8 failed because of that (already running)

 

Прикрепленные файлы:

•  com.drweb.strace.tar.gz   141,17К   2 Скачано раз

[bardo]

I don't think the problem is in iptables, I was unaware that I had ufw installed (I forgot since I don't use this installation) , anyway I uninstalled ufw and iptables was still there because it was a dependency of something else so I left it, but iptables service isn't set to start on boot and iptables is not running, what's more... with iptables-save now I get nothing, so I assume something else is the problem.

You can look at previous page where I listed all services, ufw was set to start on boot and iptables was disabled.

[dbanschikov]

Please, provide output of:

getent group drweb

[dbanschikov]

Regarding problem with OpenRC: add RC_DEBUG=yes to /etc/rc.conf and reproduce problem.

[bardo]

Please, provide output of:

getent group drweb

 

# getent group drweb
drweb:x:1002:

[bardo]

Regarding problem with OpenRC: add RC_DEBUG=yes to /etc/rc.conf and reproduce problem.

 

I did that but I never used it before so I don't know what to do next. Google didn't help.

[bardo]

I give up, don't want to trouble you anymore, it's probably something in my system, I'm sure it's working fine elsewhere, thank you for your help.

[dbanschikov]

I give up, don't want to trouble you anymore, it's probably something in my system, I'm sure it's working fine elsewhere, thank you for your help.

 

We have spent so much time on the problem and you don't want to finish it?

 

Regarding RC.

1. Uncomment rc_logger="YES"

2. Uncomment rc_vervose=yes

3. Add RC_DEBUG="YES"

4. Reboot

5. Provide /var/log/rc.log

 

Regarding problem with Spider Gate: I have reproduced problem, please be patient will provide more info soon.

[bardo]

I don't want to trouble you that's all, plus I wasn't sure if it's only me for some reason, but now that you reproduced the problem okay let's finish it

I'll get back to you little later regarding RC

[dbanschikov]

I don't want to trouble you that's all, plus I wasn't sure if it's only me for some reason, but now that you reproduced the problem okay let's finish it

I'll get back to you little later regarding RC

 

Actually I have reproduced both problems.

Don't bother yourself with RC.

I will figure out steps to mitigate both issues.

[dbanschikov]

Regarding OpenRC problem. At the moment we have only such WA: replace /etc/init.d/drweb-configd with such script:

#!/sbin/openrc-run

extra_started_commands="reload"

: ${DRWEB_BINARY:=/opt/drweb.com/bin/drweb-configd}
: ${DRWEB_PIDFILE:=/var/run/drweb-configd.pid}

depend() {
	use logger
	need localmount
	after bootmisc
}

start() {
	ebegin "Starting Dr.Web drweb-configd..."
	start-stop-daemon --start --exec "${DRWEB_BINARY}" \
		--pidfile "${DRWEB_PIDFILE}" -- -d -p ${DRWEB_PIDFILE}
	eend $?
}

stop() {
	ebegin "Stopping Dr.Web drweb-configd..."
	start-stop-daemon --stop --exec "${DRWEB_BINARY}" \
		--pidfile "${DRWEB_PIDFILE}"
	eend $?
}

reload() {
	ebegin "Reloading Dr.Web drweb-configd..."
	start-stop-daemon --signal HUP \
	    --exec "${DRWEB_BINARY}" --pidfile "${DRWEB_PIDFILE}"
	eend $?
}

We will try to fix this problem in upcoming release.

 

Spider Gate problem is still in progress.

Сообщение было изменено dbanschikov: 08 Ноябрь 2016 - 12:45

[bardo]

I can confirm that this solves RC issue.

 

As for Spider Gate, I assume kernel is not the problem ?