Jump to content
cybersecjedi

Pineapd.sock: no such file or directory

Recommended Posts

Everytime I try to start a pineap recon the following error is returned:

root@Pineapple:/tmp# pineap run_scan 0 2
Failed to connect to socket at path: /var/run/pineapd.sock: No such file or directory
I believe is because the service can't create the PineAP database and that is why the PineAP can't be enabled, this started to happen after the latest firmware upgrade 2.5.4

I've seen may people complaining about the same thing and no solutions.

I have moved the scan logs to the sd card changing the /tmp/pineap.conf file path

DMSG logs>

  13.250000] Loading modules backported from Linux version v4.4-rc5-1913-gc8fdf68
[   13.250000] Backport generated by backports.git backports-20151218-0-g2f58d9d
[   13.410000] ath: EEPROM regdomain: 0x0
[   13.410000] ath: EEPROM indicates default country code should be used
[   13.410000] ath: doing EEPROM country->regdmn map search
[   13.410000] ath: country maps to regdmn code: 0x3a
[   13.410000] ath: Country alpha2 being used: US
[   13.410000] ath: Regpair used: 0x3a
[   13.420000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   13.420000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2
[   13.440000] usbcore: registered new interface driver ath9k_htc
[   13.490000] RPC: Registered named UNIX socket transport module.
[   13.490000] RPC: Registered udp transport module.
[   13.490000] RPC: Registered tcp transport module.
[   13.500000] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   13.530000] tun: Universal TUN/TAP device driver, 1.6
[   13.530000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[   13.580000] usbcore: registered new interface driver rt2800usb
[   13.590000] usbcore: registered new interface driver rtl8187
[   13.710000] usbcore: registered new interface driver rtl8192cu
[   13.930000] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   13.940000] usbcore: registered new interface driver cdc_acm
[   13.950000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[   13.960000] usbcore: registered new interface driver cdc_wdm
[   13.980000] nf_conntrack version 0.5.0 (955 buckets, 3820 max)
[   14.010000] usbcore: registered new interface driver ums-alauda
[   14.020000] usbcore: registered new interface driver ums-cypress
[   14.030000] usbcore: registered new interface driver ums-datafab
[   14.040000] usbcore: registered new interface driver ums-freecom
[   14.040000] usbcore: registered new interface driver ums-isd200
[   14.050000] usbcore: registered new interface driver ums-jumpshot
[   14.060000] usbcore: registered new interface driver ums-karma
[   14.070000] usbcore: registered new interface driver ums-sddr09
[   14.070000] usbcore: registered new interface driver ums-sddr55
[   14.080000] usbcore: registered new interface driver ums-usbat
[   14.100000] usbcore: registered new interface driver usbserial
[   14.110000] usbcore: registered new interface driver usbserial_generic
[   14.120000] usbserial: USB Serial support registered for generic
[   14.170000] xt_time: kernel timezone is -0000
[   14.180000] usbcore: registered new interface driver asix
[   14.190000] usbcore: registered new interface driver ax88179_178a
[   14.200000] usbcore: registered new interface driver cdc_ether
[   14.200000] ip_tables: (C) 2000-2006 Netfilter Core Team
[   14.220000] usbcore: registered new interface driver pl2303
[   14.230000] usbserial: USB Serial support registered for pl2303
[   14.240000] PPP generic driver version 2.4.2
[   14.250000] NET: Registered protocol family 24
[   14.260000] usbcore: registered new interface driver qmi_wwan
[   14.270000] usbcore: registered new interface driver rndis_host
[   14.280000] usbcore: registered new interface driver sierra_net
[   14.290000] usbcore: registered new interface driver option
[   14.300000] usbserial: USB Serial support registered for GSM modem (1-port)
[   24.200000] device eth0 entered promiscuous mode
[   26.990000] eth0: link up (100Mbps/Full duplex)
[   27.020000] br-lan: port 1(eth0) entered forwarding state
[   27.020000] br-lan: port 1(eth0) entered forwarding state
[   29.020000] br-lan: port 1(eth0) entered forwarding state
[   29.470000] device wlan0 entered promiscuous mode
[   29.510000] br-lan: port 2(wlan0) entered forwarding state
[   29.520000] br-lan: port 2(wlan0) entered forwarding state
[   29.560000] device wlan0-1 entered promiscuous mode
[   29.570000] br-lan: port 3(wlan0-1) entered forwarding state
[   29.570000] br-lan: port 3(wlan0-1) entered forwarding state
[   30.560000] br-lan: port 3(wlan0-1) entered disabled state
[   31.520000] br-lan: port 2(wlan0) entered forwarding state
[   31.880000] br-lan: port 3(wlan0-1) entered forwarding state
[   31.880000] br-lan: port 3(wlan0-1) entered forwarding state
[   32.220000] random: nonblocking pool is initialized
[   33.880000] br-lan: port 3(wlan0-1) entered forwarding state

no useful logs in SYSTEM

Plus I found that the interface set by default in the PineAP log is wlan1mon which does not exist, instead I'm using a br-lan that enables the wlan0-1 interface which is new, I have of course switched the config file to point at this interface but the .db files of the PineAP daemon are still not working.

Any thoughts?

Share this post


Link to post
Share on other sites
16 hours ago, cybersecjedi said:

Everytime I try to start a pineap recon the following error is returned:

root@Pineapple:/tmp# pineap run_scan 0 2
Failed to connect to socket at path: /var/run/pineapd.sock: No such file or directory
I believe is because the service can't create the PineAP database and that is why the PineAP can't be enabled, this started to happen after the latest firmware upgrade 2.5.4

I've seen may people complaining about the same thing and no solutions.

This isn't the reason why (I also haven't seen anyone talking about this?). It's because PineAP is not running. If you insist on using it over the command line, then start it with the init script.

/etc/init.d/pineapd start

 

16 hours ago, cybersecjedi said:

I have moved the scan logs to the sd card changing the /tmp/pineap.conf file path

Do not edit the configuration file manually. Expect things to break if you're going to.

 

16 hours ago, cybersecjedi said:

Plus I found that the interface set by default in the PineAP log is wlan1mon which does not exist, instead I'm using a br-lan that enables the wlan0-1 interface which is new, I have of course switched the config file to point at this interface but the .db files of the PineAP daemon are still not working.

This is also wrong. The correct interface is wlan1mon - that isn't a mistake on our part. You need to put wlan1 into monitor mode, and using the init script I described above will do this for you. Using br-lan or any wlan0 interfaces will break a lot of other stuff, especially the Access Points.

16 hours ago, cybersecjedi said:

no useful logs in SYSTEM

"logread" (the System log in the UI) would have told you why PineAP is not running.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...