Jump to content

Postgresql won't start

pkfox

By pkfox
in Beginners

 Share

Recommended Posts

pkfox

pkfox

Posted
Posted

Hi all, i've installed Postgresql on my Nanopi M4 V2 board which is running Buster  Armbian Linux 4.4.192-rk3399 and it appears to have installed ok but it won't start - there's nothing in the logs and running pg_isready returns no response - any ideas guys

GeorgeP

GeorgeP

Posted
Posted

I've no specific postgresql experience but I have found that the way Armbian handles logging to zram can mean that the log files either don't exist or can't be written.

Generally the answer to situations like this is to try running the binary from a command prompt with the 'verbose' switch set, if it then runs OK, try to modify the sysctl files to enable logging.

 

 

pkfox

pkfox

Posted
  • Author
Posted
  On 12/15/2019 at 11:52 AM, GeorgeP said:

I've no specific postgresql experience but I have found that the way Armbian handles logging to zram can mean that the log files either don't exist or can't be written.

Generally the answer to situations like this is to try running the binary from a command prompt with the 'verbose' switch set, if it then runs OK, try to modify the sysctl files to enable logging.

 

 

Expand  

Thanks I'll give it a shot

pkfox

pkfox

Posted
  • Author
Posted
  On 12/15/2019 at 1:00 PM, pkfox said:

Thanks I'll give it a shot

Expand  

I can't even find the binary - also the install usually creates a /etc/postgresql folder which isn't happening - I've tried removing the install and reinstalling but I receive the message that it's already installed ? WTF ?

 

Igor

Igor

Posted
Posted

It looks like there is some problem but it installs perfectly on a clean Armbian Buster armhf / Cubietruck http://ix.io/24wp

 

  Reveal hidden contents

 

pkfox

pkfox

Posted
  • Author
Posted
  On 12/15/2019 at 5:40 PM, Igor said:

It looks like there is some problem but it installs perfectly on a clean Armbian Buster armhf / Cubietruck http://ix.io/24wp

 

  Reveal hidden contents

OK Igor v weird though ? I have it running perfectly on the M4 V1

Expand  

 

Igor

Igor

Posted
Posted
  On 12/15/2019 at 9:06 PM, pkfox said:

OK Igor v weird though ? I have it running perfectly on the M4 V1

Expand  


Need to do more tests to find out where is the source of this trouble. M4 V2 image is still labelled as "testing" - it is expected that you will not use it for real yet - which means this is not a big problem yet. But yes, we have to fix it.

pkfox

pkfox

Posted
  • Author
Posted
  On 12/16/2019 at 5:51 AM, Igor said:


Need to do more tests to find out where is the source of this trouble. M4 V2 image is still labelled as "testing" - it is expected that you will not use it for real yet - which means this is not a big problem yet. But yes, we have to fix it.

Expand  

Oh I'm not using it for real just trying to do something useful with it as I am with the M4 V1 , I only bought the V2 because they seem to have discontinued the V1 4gb model which is a pity as Armbian is rock solid on those.

 

Igor

Igor

Posted
Posted
  On 12/16/2019 at 7:18 AM, pkfox said:

I only bought the V2 because they seem to have discontinued the V1 4gb model which is a pity as Armbian is rock solid on those.

Expand  


Understand, but there is little we can do about. We need to adjust software. Perhaps help develop support? Its heavily sponsored from our private time which is currently covered less than 0.5%. We - people that move things forward - are 10 - 50 x too small to fix thing with the speed average user expects ;) You are frustrated since things are not working, we as well since we can't do much about ...

pkfox

pkfox

Posted
  • Author
Posted
  On 12/16/2019 at 8:10 AM, Igor said:


Understand, but there is little we can do about. We need to adjust software. Perhaps help develop support? Its heavily sponsored from our private time which is currently covered less than 0.5%. We - people that move things forward - are 10 - 50 x too small to fix thing with the speed average user expects ;) You are frustrated since things are not working, we as well since we can't do much about

Expand  

I do appreciate what you people do and if I was more knowledgeable I would contribute but I'm quite limited in my knowledge of Linux

 

Igor

Igor

Posted
Posted
  On 12/17/2019 at 12:02 AM, pkfox said:

but I'm quite limited in my knowledge of Linux

Expand  


That is great. :P You have a lot of opportunities to learn ... and help. When I started with this project, most of activities were either a blur from the past or something totally new. Persistence is the key.

 

There are lots of tasks, where no Linux know-how is needed, but has to be done. Since most people don't even notice, nobody likes to do them ... I have to do it.
 

1
pkfox

pkfox

Posted
  • Author
Posted
  On 12/17/2019 at 6:04 AM, Igor said:


That is great. :P You have a lot of opportunities to learn ... and help. When I started with this project, most of activities were either a blur from the past or something totally new. Persistence is the key.

 

There are lots of tasks, where no Linux know-how is needed, but has to be done. Since most people don't even notice, nobody likes to do them ... I have to do it.
 

Expand  

Hi Igor, I though I'd start from scratch, so , I flashed the image supplied by @pask , used the wi-fi drivers specified by @martinayotte, and applied the boot loader patch supplied by @pask. All booted fine with wi-fi working , so I attempted to install postgresql. And it worked perfectly, don't know why but I must have screwed something up before - good news is it works, bad news is I don't know why - thanks for your help.

pask

pask

Posted
Posted
  On 12/17/2019 at 3:32 PM, pkfox said:

Hi Igor, I though I'd start from scratch, so , I flashed the image supplied by @pask , used the wi-fi drivers specified by @martinayotte, and applied the boot loader patch supplied by @pask. All booted fine with wi-fi working , so I attempted to install postgresql. And it worked perfectly, don't know why but I must have screwed something up before - good news is it works, bad news is I don't know why - thanks for your help.

Expand  

@pkfox It's time to use WIP images for this board https://www.armbian.com/nanopi-m4-v2/

No need anymore for patchs or other magics.

 

Anyway, my experience is that the 4.4.y images still don't work for me. While the ones with buster 5.4 kernel work, but I'm still struggling to get anything really useful done as I'm still experiencing some unreliable behavior, like sudden freezes when connecting be means of tigervnc.  Perhaps my board is an unlucky sample.

 

Let us know if you experience goes better.

pkfox

pkfox

Posted
  • Author
Posted
  On 12/17/2019 at 8:39 PM, pask said:

@pkfox It's time to use WIP images for this board https://www.armbian.com/nanopi-m4-v2/

No need anymore for patchs or other magics.

 

Anyway, my experience is that the 4.4.y images still don't work for me. While the ones with buster 5.4 kernel work, but I'm still struggling to get anything really useful done as I'm still experiencing some unreliable behavior, like sudden freezes when connecting be means of tigervnc.  Perhaps my board is an unlucky sample.

 

Let us know if you experience goes better.

Expand  

Hi @pask are you saying I can flash the image you gave a link to and it will boot and wifi will work ? your original images were about 1gb and these are only 300mb ish is this correct ?

 

piter75

piter75

Posted
Posted
  On 12/17/2019 at 8:39 PM, pask said:

my experience is that the 4.4.y images still don't work for me

Expand  

Is it still the issue that as soon as you connect UART it stops working?

 

The other thing that does not work in 4.4.x right now is networking :(

 

I was able to fix wireless with the following addition to the NetworkManager's config file.

 

/etc/NetworkManager/NetworkManager.conf 

[device]
wifi.scan-rand-mac-address=no

Wired connection is another beast. As soon as it connects and receives IP address it becomes totally slow, unreliable and starts dropping packets.

I tried to make the Frankenstein image your way (M4 image + rockpi's u-boot) and it behaves the same.

OTOH FriendlyARM's image has stable wired connection and I cannot find the reason why, yet :(

pkfox

pkfox

Posted
  • Author
Posted
  On 12/17/2019 at 9:53 PM, pask said:

I you scroll down the page https://www.armbian.com/nanopi-m4-v2/

you'll find the fat desktop images too.

 

Expand  

Hey good work @pask - flashed it straight to eMMC and it booted - no WiFi though :-( - I tried copying the broadcom drivers I've been using with your original image but no joy - using armbian-config my network is shown but won't connect ( fails with no reason given ) tried it from cli nmcli but same error message

pkfox

pkfox

Posted
  • Author
Posted
  On 12/17/2019 at 10:40 PM, piter75 said:

Is it still the issue that as soon as you connect UART it stops working?

 

The other thing that does not work in 4.4.x right now is networking :(

 

I was able to fix wireless with the following addition to the NetworkManager's config file.

 

/etc/NetworkManager/NetworkManager.conf 

[device]
wifi.scan-rand-mac-address=no

Wired connection is another beast. As soon as it connects and receives IP address it becomes totally slow, unreliable and starts dropping packets.

I tried to make the Frankenstein image your way (M4 image + rockpi's u-boot) and it behaves the same.

OTOH FriendlyARM's image has stable wired connection and I cannot find the reason why, yet :(

Expand  

Good man WiFi now works - thanks very much - maybe @pask can add those lines to his build - did I need to use the drivers from @pask original build ? or will the ones in the new build work ok

pask

pask

Posted
Posted
  On 12/17/2019 at 10:40 PM, piter75 said:

Is it still the issue that as soon as you connect UART it stops working?

 

The other thing that does not work in 4.4.x right now is networking :(

 

Expand  

 

Hello @piter75

Thank you! Now I understand why I'm not able to reach the nanopim4-v2 with a buster/4.4x sd image through the wired network. 

 

BTW I've not anymore connected my serial dongle to the m4v2, as I've moved the board from my desktop to an "intended production" position, and I'm using it headless and wired connected.

 

The 5.4.2 buster image works quite well in server mode (wired network, usb, and so on). Still troubles when in desktop mode as I have experienced frequent freezes that make it unusable. Even when connected via a tigervnc client to a tigervnc server there are frequent freezes of the xfce desktop environment. But the board itself doesn't freeze: indeed, if I close the tigervnc client window once frozen,  when I reconnect to the tigervnc server, I can continue using the desktop, at least until the next freeze.

I suspect It's not a tigervnc specific issue, as I've also tried x2go and experienced a similar behavior.

 

  On 12/17/2019 at 11:28 PM, pkfox said:

Good man WiFi now works - thanks very much - maybe @pask can add those lines to his build - did I need to use the drivers from @pask original build ? or will the ones in the new build work ok

Expand  

 

 Thank you too @pkfox. 

Actually who deserves our kudos are the great armbian developers, and among them I can cite @piter75, who has made possible to us the use of the great armbian OS on this board.

 

pkfox

pkfox

Posted
  • Author
Posted
  On 12/18/2019 at 7:50 AM, pask said:

 

Hello @piter75

Thank you! Now I understand why I'm not able to reach the nanopim4-v2 with a buster/4.4x sd image through the wired network. 

 

BTW I've not anymore connected my serial dongle to the m4v2, as I've moved the board from my desktop to an "intended production" position, and I'm using it headless and wired connected.

 

The 5.4.2 buster image works quite well in server mode (wired network, usb, and so on). Still troubles when in desktop mode as I have experienced frequent freezes that make it unusable. Even when connected via a tigervnc client to a tigervnc server there are frequent freezes of the xfce desktop environment. But the board itself doesn't freeze: indeed, if I close the tigervnc client window once frozen,  when I reconnect to the tigervnc server, I can continue using the desktop, at least until the next freeze.

I suspect It's not a tigervnc specific issue, as I've also tried x2go and experienced a similar behavior.

 

 

 Thank you too @pkfox. 

Actually who deserves our kudos are the great armbian developers, and among them I can cite @piter75, who has made possible to us the use of the great armbian OS on this board.

 

Expand  

I've now redone the whole process from scratch thus ( I did this using a Linux box and a USB TTL serial cable)

 

1) Download an image from @pask link

2) Start a terminal

3) cd to the folder containing your download

4) Unzip your download to extract the *.img file

5) Connect an sdcard or eMMC to your pc ( I used a transcend adapter )

6) Run lsblk to identify your device, in my case it returned /dev/sdc

7) Run mount to ensure it is not mounted and unmount it if necessary ( umount /dev/sdc or umount /dev/sdc1 )

8) Run dd if =NameOfYourImage.img of=/dev/sdc status=progress

9) When completed ( it takes a while ) make a directory to enable you to mount your device ( mkdir /mnt/MyDevice)

10) Run mount /dev/sdc1 /mnt/MyDevice

11) nano /mnt/MyDevice/etc/NetworkManager/NetworkManager.conf

12) Add these two lines and save the file

[device]
wifi.scan-rand-mac-address=no

 

13) Unmount the device (umount /mnt/MyDevice)

14) Put the device( sdcard or eMMC ) in the M4 - DO NOT APPLY POWER YET !

15) Connect a serial cable to the UART pins on the board and attach the other end to a USB port on your PC

16) Issue this command picocom -b 1150000 /dev/ttyUSB0 ( I'm typing this at work but I think this is correct ) this should connect you to the M4

16) Apply power to the M4 and you should see the boot output

15) Login as root with password 1234 ( you'll be prompted to change the password )

17) Run armbian-config to configure wifi

18) Ensure you have an ip address ( ip a ) and look for wlan0

19) Reboot the M4 having removed the serial cable first.

 

In my case It all worked - your case may be different.

 

 

 

 

 

 

 

piter75

piter75

Posted
Posted
  On 12/18/2019 at 7:50 AM, pask said:

I understand why I'm not able to reach the nanopim4-v2 with a buster/4.4x sd image through the wired network

Expand  

I hopefully managed to fix networking in legacy kernel. At least it works well on my unit now ;-)

It is merged into master and downloadable images are also recreated.

 

  On 12/18/2019 at 7:50 AM, pask said:

troubles when in desktop mode as I have experienced frequent freezes that make it unusable. Even when connected via a tigervnc client to a tigervnc server there are frequent freezes

Expand  

I am wondering whether it may have something to do with Panfrost gpu driver being not really stable yet.

Maybe VNC is also using gpu to accelerate desktop drawing...

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept