[Résolu moi-même][NOT RESOLVABLE-RESOLUTION FAILURE] Mailtrail doesn't work

[Darkopnsense]

Hello,

In general I have the message:
Updates in this section need also a restart via sensor or server menu.

As Maltrail doesn't work and I can't find the way,

I would like to know what its path is in console mode.
I am looking for the installation directory of SENSOR and SERVER to start it in manual.


Regards,

[Darkopnsense]

Hello,

I found

/usr/local/share/maltrail/maltrail.conf

but the following commands do not work,

python sensor.py
python server.py

what is the PYTHON instruction under freebsd & opnsence ?

Regards,

[fabian]

You need to append the version like for example python2.7

[Darkopnsense]

Thank you

[Darkopnsense]

Hello,

After entering the correct synthax in console mode, I do not know why MALTRAIL still does not work.

It always shows me in maltrail / general: "Updates to this section also require a restart via the Sensor or Server menu."

Although in dashboard / services / maltrailderver is activated, also in console mode (Sensor & server = running).

But I am nothing by consulting the port 8338 on my local ip.

It worked for several weeks, but now maltrail does not activate on my configurations, I would like to know who or who is blocking this plugin from me.

I only monitor the wan.

Would there be an activity log to consult and where?

An idea ?

Regards,

[mimugmail]

This is just a info which stays forever so you know that when you change something in general you also have to save in server/sensor to make them active.

[Darkopnsense]

thank you,

I don't understand the meaning of your answer, maybe translation problem.

After modification, what to do in server / sensor?

Regards,

[Darkopnsense]

sensor asks me to install 'schedtool'

I don't know where to find the version for freebsd.

If you can give me an "http" link to deploy it with wget

Thank you.

Looking forward to hearing from you,

Regards,

[mimugmail]

thank you,

I don't understand the meaning of your answer, maybe translation problem.

After modification, what to do in server / sensor?

Regards,

Just hit "Save"

[Darkopnsense]

Thank you for the answer.

It’s a good joke.

Of course, I am going first in the submenus of MALTRAIL (general, sensor, server) to save and see if it changes anything.

So this is not the right track.

Regards,

[Darkopnsense]

I have a reflection.

The following plugins are functional:
etpro-telemetry is in python3.7
sensei is in python3.7

While the malfunctioning plugin does not work on a module:
pcapy is in python2.7

Regards,

[mimugmail]

Maybe at first check if the port is really listening, via CLI:

sockstat -4 | grep 8338

[Darkopnsense]

Thank you for the answer.

Here is the return of the order:

root@Pare-Feu:/ # sockstat -4 | grep 8338
root     python2.7  52758 3  tcp4   192.168.66.66:8338    *:*

This does not speak to me, I do not know how to interpret the result.

Regards,

[franco]

From a purely technical perspective, Python 2.7 and 3.7 do neatly coexist so we need a relevant error or health audit issue to assume it does not.


Cheers,
Franco

[mimugmail]

Thank you for the answer.

Here is the return of the order:

root@Pare-Feu:/ # sockstat -4 | grep 8338
root     python2.7  52758 3  tcp4   192.168.66.66:8338    *:*

This does not speak to me, I do not know how to interpret the result.

Regards,

So the server is running on port 8338. What happens when you surf to this IP with http (not https)?
Do you get an error? Blocked packet?