Cannot finish connecting on OpenWrt

Technical Support
#1

Hello,

I cannot finish the connecting when I start “connect” on mudfish page. There 3 results when connecting:

  1. hangs at 10%
  2. hangs at 96%
  3. The mudfish web page gone, says cannot reach that page.

And when I try to see the mudfish page, it requires me to login again.
I see twice warnings - "MUDEC_00371: mudflow process isn’t found. Crash? Exits the launcher"

Launcher Log

[STDOUT]
Sun, 05 Jan 2025 03:23:02 GMT [0.023339] param [WARN]  Failed to open /opt/mudfish-pi/2.6.8/var/.conf file.
Sun, 05 Jan 2025 03:23:02 GMT [0.024798] run  [INFO]  Checking the WAN network reachable to 14.63.223.218:443 (count 0).
Sun, 05 Jan 2025 03:23:02 GMT [0.097017] run  [INFO]  Good.  Reached to the WAN network (14.63.223.218:443).
Sun, 05 Jan 2025 03:23:02 GMT [0.097312] rtt  [INFO]  Fetchs the static node information.
Sun, 05 Jan 2025 03:23:02 GMT [0.097348] httpd [INFO]  Listening 192.168.2.1:8282
Sun, 05 Jan 2025 03:23:02 GMT [0.097506] run  [INFO]  Skipped to launch the default browser to 192.168.2.1:8282
Sun, 05 Jan 2025 03:28:54 GMT [352.088662] param [WARN]  Failed to open /opt/mudfish-pi/2.6.8/var/.conf for writing.
Sun, 05 Jan 2025 03:28:54 GMT [352.088788] param [WARN]  Failed to open /opt/mudfish-pi/2.6.8/var/.conf for writing.
Sun, 05 Jan 2025 03:28:56 GMT [353.611187] param [WARN]  Failed to open /opt/mudfish-pi/2.6.8/var/.conf for writing.
No mudrun_stderr.txt exists

Here’s my openwrt machine info ubus call system board

{
	"kernel": "5.15.134",
	"hostname": "OpenWrt",
	"system": "ARMv8 Processor rev 4",
	"model": "Xiaomi Redmi Router AX6000 (stock layout)",
	"board_name": "xiaomi,redmi-router-ax6000-stock",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "23.05.0",
		"revision": "r23497-6637af95aa",
		"target": "mediatek/filogic",
		"description": "OpenWrt 23.05.0 r23497-6637af95aa"
	}
}

Related packages:
mudfish-pi (2.6.9-1)
luci-app-mudfish-pi (git-24.225.74088-5035535)

And it’s weird that - OpenWrt shows ‘2.6.9’ mudfish-pi installed. But on Mudfish page, it shows ‘2.6.8’, and launcher log show it trys to access “/opt/mudfish-pi/2.6.8”, and I have only “/opt/mudfish-pi/2.6.9/” on my device

#2

:frowning: It looks like mudfish packages were built in wrong way. Let me create a fresh image. Sorry for this inconvenience.

At this point I’d triggered a build for OpenWRT 23.05 but I guess that the build takes at least 24 ~ 36 hours to be completed. If the build worked well, it’ll be found at Index of /releases/openwrt/packages-23.05/mediatek-filogic/base/ link.

#3

@weongyo,

I see timestamp changes to 07-Jan-2025 for luci and base at Index of /releases/openwrt/packages-23.05/mediatek-filogic/

But the results are the same, are the packages still building?

Tue, 07 Jan 2025 21:18:36 GMT [0.022954] param [WARN]  Failed to open /opt/mudfish-pi/2.6.8/var/.conf file.
Tue, 07 Jan 2025 21:18:36 GMT [0.024399] run  [INFO]  Checking the WAN network reachable to 14.63.223.218:443 (count 0).
Tue, 07 Jan 2025 21:18:36 GMT [0.098025] run  [INFO]  Good.  Reached to the WAN network (14.63.223.218:443).
Tue, 07 Jan 2025 21:18:36 GMT [0.098339] rtt  [INFO]  Fetchs the static node information.
Tue, 07 Jan 2025 21:18:36 GMT [0.098374] httpd [INFO]  Listening 192.168.2.1:8282
Tue, 07 Jan 2025 21:18:36 GMT [0.098548] run  [INFO]  Skipped to launch the default browser to 192.168.2.1:8282
Tue, 07 Jan 2025 21:19:00 GMT [24.255019] param [WARN]  Failed to open /opt/mudfish-pi/2.6.8/var/.conf for writing.
Tue, 07 Jan 2025 21:19:00 GMT [24.255144] param [WARN]  Failed to open /opt/mudfish-pi/2.6.8/var/.conf for writing.
Tue, 07 Jan 2025 21:19:00 GMT [24.255216] param [WARN]  Failed to open /opt/mudfish-pi/2.6.8/var/.conf for writing.

root@OpenWrt:~# opkg list mudfish-pi
mudfish-pi - 2.6.9-1
root@OpenWrt:~# opkg list luci-app-mudfish-pi mudfish-pi
luci-app-mudfish-pi - git-24.225.74088-5035535
#4

:frowning: Ooops. My bad. I found a bug at 2.6.9 packages. At this moment I’d fixed the issue and triggered another build. If it’s not broken, new build will be available within 5 ~ 6 hours.

#5

Hello weongyo,

I’ve tried the release today, the issue is fixed.

Thanks

1 Like