"There is no active user" when setting up Xray to write logs to files

[AlexKoup]

I found a problem. If the xray_config.json file specifies saving logs to files like this:

   "log": {
     "loglevel": "info",
         "access": "/var/lib/marzban-node/access.log",
         "error": "/var/lib/marzban-node/error.log"
   },

then the script does not work, it displays "There is no active user".
Right while the script was running, I deleted and added back the access and error entries, restarted Xray and the script either worked or stopped.

[houshmand-2005]

hom this is odd, it shouldn't be a problem
maybe because of the config update there is a problem with getting the log from the panel. When you run script after saving the changes does the problem persist?
Anyway if this problem still exists I suggest you discuss this issue with Marzban, because getting logs from Xray core and sending logs is done by the panel.

[AlexKoup]

Yes, the problem persists even after rebooting the server and restarting marzban. The xray logs themselves are created correctly. They contain user IPs and all other information. Marzban displays logs in the panel. Only V2IpLimit stops working. It continues to write log and send messages in telegram, but there is always “There is no active user”. As soon as I remove these lines from the Xray config, even without rebooting the kernel, V2IpLimit immediately, according to the timer, starts working correctly.
Because I write logs on all nodes, then in the marzban docker-compose.yml I have the following volume connected:

• /var/lib/marzban/logs:/var/lib/marzban-node

[houshmand-2005]

I checked myself.
After change config(xray_config.json) like this

"log": {
    "loglevel": "info",
    "access": "access.log",
    "error": "error.log"
  },

This is what Api and Panel shows (script receives logs like this):

Xray 1.8.4 (Xray, Penetrates Everything.) Custom (go1.21.0 linux/amd64)

A unified platform for anti-censorship.
2023/11/22 16:59:16 [Info] infra/conf/serial: Reading config: stdin:

And this is the contents of access.log file (this is right):

2023/11/22 17:01:32 192.168.1.33:11421 accepted tcp192.168.1.36:443 [VLESS_INBOUND -> proxy] email: 1.Test
2023/11/22 17:01:36 192.168.1.33:11424 accepted tcp192.168.1.36:443 [VLESS_INBOUND -> proxy] email: 1.Test
2023/11/22 17:01:37 192.168.1.33:11430 accepted tcp192.168.1.36:443 [VLESS_INBOUND -> proxy] email: 1.Test

The xray logs themselves are created correctly. They contain user IPs and all other information. Marzban displays logs in the panel. @AlexKoup

And that's why I don't know how you can see the users' information inside the panel logs. Please check it again.
You probably see the logs before the core is restarted.

---

As I can understand when with Xray you save the logs Xray doesn't show them on stdout, so marzban can't catch them.
This is Marzban code to get logs:

    ...
    def capture_only():
        while self.process:
            output = self.process.stdout.readline()
            if output:
                output = output.strip()
                ...

so marzban just read the stdout and when Xray is saving log file, it doesn't send logs into stdout.

This is my opinion, maybe I'm wrong :)

[AlexKoup]

It looks like it is. That is, writing logs to files and working with V2IpLimit are incompatible on marzban. Is it possible to force the script to read logs from xray files?

[GawrAme]

i had the same issues here

[houshmand-2005]

@AlexKoup Not by default, but it can be changed.
But you know this isn't a good way because we can't support nodes in this way.
As a result, if Marzban finds a way to send logs in this mode (which is not easy because Xray itself has limitations for it), which is not a problem, otherwise it's not easy solve problem.

I will create an issue in Marzban to report it.