Getting to transmission webgui

Status
Not open for further replies.

matlock

Contributor
Joined
Mar 2, 2012
Messages
114
So i've upgraded to 8.2 RC1 - deleted the jail and plugins and then reinstalled them. I can't seem to get the transmission webgui.

I setup the jail to have an ip of 192.168.1.96

In the past on the screen for freenas with a monitor hooked up (options 1-11) i would see two ipaddresses. 1 for the freenas webui itself, and then the jail ip address.

The jail ip address is showing up as 0.0.0.0- somethings obviously wrong.
I can't get to the transmission webui.

Is this a known issue? Is there a work around? Or am i missing something?
 

matlock

Contributor
Joined
Mar 2, 2012
Messages
114
So i've upgraded to 8.2 Release p1 x64- i've installed the jail & plugins fresh- yet i still can't access the transmission webgui.

My freenas ip is 192.168.1.97
The jail ip is 192.168.1.96

going to 192.168.1.96:9091 doesn't load anything. Has anyone else seen this? Or having similar issues?
 

ProtoSD

MVP
Joined
Jul 1, 2011
Messages
3,348
I don't use transmission, so this is just a guess, did you enable the plugin/turn it On?
 

matlock

Contributor
Joined
Mar 2, 2012
Messages
114
Oh but of course the jail & plugin is turned on =) thanks for checking though

How can I confirm that the jail's ip is 'working'?
 

ProtoSD

MVP
Joined
Jul 1, 2011
Messages
3,348
you can ping the ip address of the jail from freenas. Open a shell from the GUI, then just "ping 192.168.1.96"
 

matlock

Contributor
Joined
Mar 2, 2012
Messages
114
Should a ping work from my windows pc? opening a cmd prompt and pinging the jail ip?
 

ProtoSD

MVP
Joined
Jul 1, 2011
Messages
3,348
yes

You could check to see if transmission is actually running in the jail by doing:

jexec 1 ps auxw


There should probably be 2 processes that say transmission

Sorry, I'd probably be more help if I just downloaded it and installed it to see :)

Hopefully someone that actually uses it can help you better!
 

fyver

Dabbler
Joined
Apr 23, 2012
Messages
21
So i've upgraded to 8.2 Release p1 x64- i've installed the jail & plugins fresh- yet i still can't access the transmission webgui.

My freenas ip is 192.168.1.97
The jail ip is 192.168.1.96

going to 192.168.1.96:9091 doesn't load anything. Has anyone else seen this? Or having similar issues?

I'm having exactly the same problem... I can ping the jail from within freenas and if I check what is running in the jail I see 2 transmission processes.
But i can't connect to the transmission interface either and I can't ping the jail from my laptop...
 

matlock

Contributor
Joined
Mar 2, 2012
Messages
114
Similarly to Fyver- i can ping the jail from the shell within freenas- but i cannot ping the jail from outside of the jail (any laptop/desktop on my network).

I also see the transmission process running from the "display system processes" screen.

I feel as though i've seen plenty of posts regarding others having issues pinging the jail from outside of the jail. I'll look around to see if i find anything. In the meantime if i havnt posted links in this thread relating back to those 'outside the jail ping' issues can someone else post them to me here? Thanks.
 

matlock

Contributor
Joined
Mar 2, 2012
Messages
114
if i do an ifconfig -a here's what i get.

Code:
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=98<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
        ether 00:0c:29:81:8f:b7
        inet 192.168.1.97 netmask 0xffffff00 broadcast 192.168.1.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=3<RXCSUM,TXCSUM>
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
        inet6 ::1 prefixlen 128
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether ae:88:a8:9c:d9:05
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
        member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 4 priority 128 path cost 2000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:22:8f:00:04:0a
        inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
[\code]
 

matlock

Contributor
Joined
Mar 2, 2012
Messages
114
(not sure what happend to that last post but...)
if i do an ifconfig -a this is what i get

Code:

em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=98<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
        ether 00:0c:29:81:8f:b7
        inet 192.168.1.97 netmask 0xffffff00 broadcast 192.168.1.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=3<RXCSUM,TXCSUM>
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
        inet6 ::1 prefixlen 128
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether ae:88:a8:9c:d9:05
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
        member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 4 priority 128 path cost 2000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:22:8f:00:04:0a
        inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
[\code]
 

matlock

Contributor
Joined
Mar 2, 2012
Messages
114
looks like the post i was thinking of is not similar to the issue i'm having-
http://forums.freenas.org/showthread.php?7600-Plugins-service-problems/page2

But comparing the ifconfig's - looks like the 'epair adapter' is whats configured for their jail. My 'epair adapter' doesn't seem to be configured for my jail ip address?

(on a side note- i'm not sure where my ifconfig -a post is going- maybe needs a moderators approval?)
 

paleoN

Wizard
Joined
Apr 22, 2012
Messages
1,402
In the past on the screen for freenas with a monitor hooked up (options 1-11) i would see two ipaddresses. 1 for the freenas webui itself, and then the jail ip address.

The jail ip address is showing up as 0.0.0.0- somethings obviously wrong.
This is likely your whole problem. The database seems to be remembering the old jail alias and it's breaking the new networking.

But comparing the ifconfig's - looks like the 'epair adapter' is whats configured for their jail. My 'epair adapter' doesn't seem to be configured for my jail ip address?
I would try deleting any installed plugins, deleting the jail, saving your config, write 8.2.0-RELEASE-p1 to a new USB drive, import your old config and reinstall jail & plugins. That will often solve these types of database issues.
 

matlock

Contributor
Joined
Mar 2, 2012
Messages
114
Thank you for the suggestion- but this is a fresh installation of the Freenas 8.2 release p1 and fresh jails .... BUTTT your suggestion an idea of "dirty config" data got me thinking.

I've loaded my config file in every situation and have yet to config the jail and plugins on a "fresh" setup without loading my config file. I'll give this a shot and report back.
 

William Grzybowski

Wizard
iXsystems
Joined
May 27, 2011
Messages
1,754
This are all assumptions, it is time to provide real data...

# ifconfig -a
# netstat -rn
# jexec 1 ifconfig -a
# jexec 1 ps auxww

I see you said you've posted it but needs moderator approval... probably because it is too long, use pastebin.com or something...

But yes, you should be able to ping the jail ip from the network... if it doesnt might be something in your switch/router... you could try using a different IP for the jail (dirty ARP table or something)
 

matlock

Contributor
Joined
Mar 2, 2012
Messages
114
ifconfig -a
Code:
# ifconfig -a
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=98<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
        ether 00:0c:29:81:8f:b7
        inet 192.168.1.97 netmask 0xffffff00 broadcast 192.168.1.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=3<RXCSUM,TXCSUM>
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
        inet6 ::1 prefixlen 128
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether ae:88:a8:9c:d9:05
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
        member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 4 priority 128 path cost 2000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:22:8f:00:04:0a
        inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
[\code]

netstat -rn
Code:
netstat -rn
Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
0.0.0.0/8          link#4             U           0        0 epair0 =>
default            192.168.1.1        UGS         0     1819    em0
127.0.0.1          link#2             UH          0     4065    lo0
192.168.1.0/24     link#1             U           0   145897    em0
192.168.1.97       link#1             UHS         0       91    lo0

Internet6:
Destination                       Gateway                       Flags      Netif Expire
::1                               ::1                           UH          lo0
fe80::%lo0/64                     link#2                        U           lo0
fe80::1%lo0                       link#2                        UHS         lo0
ff01:2::/32                       fe80::1%lo0                   U           lo0
ff02::%lo0/32                     fe80::1%lo0                   U           lo0
[\code]

jexec 1 ifconfig -a
Code:
jexec 1 ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=3<RXCSUM,TXCSUM>
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:22:8f:00:05:0b
        inet 192.168.1.96 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::22:8fff:fe00:50b%epair0b prefixlen 64 scopeid 0x2
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
[\code]

jexec 1 ps auxww
Code:
jexec 1 ps auxww
USER           PID %CPU %MEM   VSZ   RSS  TT  STAT STARTED      TIME COMMAND
root          2915  0.0  0.0  6924  1000  ??  IsJ   3:46AM   0:00.10 /usr/sbin/syslogd -ss
transmission  2994  0.0  0.2 30624 11804  ??  SsJ   3:46AM   0:08.67 /usr/pbi/transmission-amd64/bin/transmission-daemon -c /usr/pbi/transmission-amd64/etc/transmission/home/Downloads -g /usr/pbi/transmission-amd64/etc/transmission/home -w /usr/pbi/transmission-amd64/etc/transmission/home/Downloads -x /usr/pbi/transmission-amd64/etc/transmission/transmission.pid -Y -gsr 2 -B -t -P 51413 --utp -l 60 -m -o -p 9091 -L 240
root          3061  0.0  0.0  7980  1148  ??  IsJ   3:46AM   0:00.11 /usr/sbin/cron -s
root          3195  0.0  0.3 74868 23984  ??  IsJ   3:46AM   0:04.26 /usr/pbi/transmission-amd64/bin/python /usr/pbi/transmission-amd64/control.py start 192.168.1.96 12346
root         13783  0.0  0.0  8048  1048   1  R+J   4:57PM   0:00.00 ps auxww
[\code]
 

matlock

Contributor
Joined
Mar 2, 2012
Messages
114
View attachment troubleshooting_transmission_plugin.txt
Just made a post- awaiting a mod again- attached is the txt file. not really sure how to use pastebin but hopefully this works.

In one of my attempts i did try a different IP address for the jail but had no luck.

(just so i understand what the 4 commands are that i'm running can you give me a 'brief' breakdown of what each 'tells' you?)

*edit* haha got the code syntax all wrong it appears =) go me!
 

William Grzybowski

Wizard
iXsystems
Joined
May 27, 2011
Messages
1,754
Not sure why epair0a has the 0.0.0.0

Try:

# ifconfig epair0a inet delete

Paste:

# jexec 1 sockstat -4

I can't really tell why you cant ping jail IP from the windows machine, I don't think the epair0a as 0.0.0.0 is related bu dont hurt trying...
 

matlock

Contributor
Joined
Mar 2, 2012
Messages
114
jexec 1 sockstat -4
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
root python 3195 3 tcp4 192.168.1.96:12346 *:*
transmission transmissi2994 6 udp4 *:* *:*
transmission transmissi2994 7 tcp4 *:9091 *:*
transmission transmissi2994 8 tcp4 *:51413 *:*
transmission transmissi2994 10 udp4 *:51413 *:*
transmission transmissi2994 12 udp4 192.168.1.96:25704 192.168.1.1:5351
 
Status
Not open for further replies.
Top