I had the some question some time ago .... - where is the directory util - until I realized that this path seems to refer to a location on GitHUB. You can find there the whole script text, mark it, copy it into the clipboard and then create a new file with the name weewx-multi and copy the clipboard content into it and save it. Then you have the weewx-multi script. Where you place in the beginning it is your choice - you are supposed to overwrite the weex script in /etc/init.d with the weewx-multi (1. rename the existing /etc/init.d/weewx: sudo mv /etc/init.d/weewx /etc/init.d/weewx-old 2. assuming you have created the weewx-multi script in /home/pi you would then rename and move it to /etc/init.d as weewx: sudo mv /home/pi/weewx-multi /etc/init.d/weewx) If you saved the weewx-multi script somewhere else you have to take that path as your source for the mv command.

On 03.02.2021 22:26, [email protected] wrote:

Thank you for the reply, Gary. I probably did something wrong with the weewx-multi init script. On a raspian, where is:
util/init.d/weewx-multi
?
I didn't copy it from it's installation path, I made a new file and pasted it into notepad++ and uploaded it with winscp. And by writing this, I think this is what my problem is all about: \r\n linebreaks in the init script file instead of \n...
gjr80 schrieb am Dienstag, 2. Februar 2021 um 22:18:15 UTC+1:

    weewx-multi works fine under WeeWX 4. I am am running a dual
    instance under raspberry Pi OS and have had no problems at all.

    Gary

    On Wednesday, 3 February 2021 at 06:27:55 UTC+10
    [email protected] wrote:

        I have the same question: is the script still valid with weewx4?

        When I try to run weewx-multi following the guide at
        https://github.com/weewx/weewx/wiki/weewx-multi
        <https://github.com/weewx/weewx/wiki/weewx-multi> I get:

        Feb 02 21:25:22 raspberrypi3B systemd[1]: Starting LSB:
        weewx-multi...
        -- Subject: A start job for unit weewx.service has begun execution
        -- Defined-By: systemd
        -- Support: https://www.debian.org/support
        <https://www.debian.org/support>
        --
        -- A start job for unit weewx.service has begun execution.
        --
        -- The job identifier is 1362.
        Feb 02 21:25:22 raspberrypi3B systemd[3728]: weewx.service:
        Failed to execute command: No such file or directory
        Feb 02 21:25:22 raspberrypi3B systemd[3728]: weewx.service:
        Failed at step EXEC spawning /etc/init.d/weewx: No such file
        or directory
        -- Subject: Process /etc/init.d/weewx could not be executed
        -- Defined-By: systemd
        -- Support: https://www.debian.org/support
        <https://www.debian.org/support>
        --
        -- The process /etc/init.d/weewx could not be executed and failed.
        --
        -- The error number returned by this process is ERRNO.
        Feb 02 21:25:22 raspberrypi3B systemd[1]: weewx.service:
        Control process exited, code=exited, status=203/EXEC
        -- Subject: Unit process exited
        -- Defined-By: systemd
        -- Support: https://www.debian.org/support
        <https://www.debian.org/support>
        --
        -- An ExecStart= process belonging to unit weewx.service has
        exited.
        --
        -- The process' exit code is 'exited' and its exit status is 203.
        Feb 02 21:25:22 raspberrypi3B systemd[1]: weewx.service:
        Failed with result 'exit-code'.
        -- Subject: Unit failed
        -- Defined-By: systemd
        -- Support: https://www.debian.org/support
        <https://www.debian.org/support>
        --
        -- The unit weewx.service has entered the 'failed' state with
        result 'exit-code'.
        Feb 02 21:25:22 raspberrypi3B systemd[1]: Failed to start LSB:
        weewx-multi.
        -- Subject: A start job for unit weewx.service has failed
        -- Defined-By: systemd
        -- Support: https://www.debian.org/support
        <https://www.debian.org/support>
        --
        -- A start job for unit weewx.service has finished with a failure.
        --
        -- The job identifier is 1362 and the job result is failed.


        [email protected] schrieb am Mittwoch, 13. Mai 2020 um
        10:50:24 UTC+2:

            Hi
            Is this script still valid using Weewx 4?

            Basically , I want to have 3 WeeWx instances pointing to 3
            different domains on 1 computer, each domain with
            different configuration. All 3 instances should read from
            the same mqtt subscription port and using Interceptor. Can
            all 3 Interceptor extensions listen to the same port or
            must Interceptor  listen to a unique ports, say 8001, 8002
            and 8003.

            I'll be using Belchertown and mqtt for all 3 domains. More
            or less the same question here with Mosquitto. Can I use
            the  same ports(1883 for mqtt and 9001 for sockets) for
            all domains or should I setup different ports for each domain.

            Thanks
            Gert


            On Friday, January 6, 2017 at 2:17:16 AM UTC+1, mwall wrote:

                On Thursday, January 5, 2017 at 7:36:48 PM UTC-5,
                tomnykds wrote:

                    Best I can tell, you can run only one weather
                    station per weewx process instance, but is there
                    any reason multiple instances can't be run on the
                    same host from per-station directories (installs
                    and configs of weewx)?  To further complicate
                    things, can all the archive data be hosted on a
                    single MySQL process as long at the database names
                    are unique?


                chris,

                just to be clear: you can run any number of weewx
                instances from a single weewx installation on a single
                computer.  each instance must have its own config
                file, database, and reports directory (if the instance
                emits any html/text/images).

                no need to modify the weewx-multi init script - just
                put the list of instance names in /etc/default/weewx-multi

                m

--
You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/1b10a764-2192-4e3f-b45d-c661f7629fbcn%40googlegroups.com <https://groups.google.com/d/msgid/weewx-user/1b10a764-2192-4e3f-b45d-c661f7629fbcn%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d92199a6-0717-f687-602f-5f9850032390%40gmail.com.

Reply via email to