skip to content »

centr-geoteh.ru

Usr ports updating permission denied

usr ports updating permission denied-42

To remove the existing module, and then install emonhub, enter the following command line; NOTE - This update will not orphan or alter your input processes, feeds, visualizations or feed data, as it only changes the way in which data is fed to emoncms.2) To install emonhub on an system where the raspberry pi module is Then disable the serial console by editing /etc/inittab and /boot/Firstly edit the inittab file by adding a '#' to the beginning of the last line, so it reads; # T:respawn:/sbin/getty -L tty AMA0 115200 vt100 ​..edit the file by changing the single line to; dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait (The reference to mmcblk0p2 may be different on your installation, depending if you are using a SD card for your root, or an external HDD) Problems?

usr ports updating permission denied-1

configure: error: Can't find Tcl configuration definitions Command failed: cd /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base && CC=/usr/bin/cc OBJC=/usr/bin/cc ./configure --prefix=/opt/local --with-tclpackage=/Library/Tcl --with-install-user=root --with-install-group=admin --with-directory-mode=0755 --enable-readline && make SELFUPDATING=1 && make install SELFUPDATING=1 Exit code: 1 Error: Error installing new Mac Ports base: command execution failed To report a bug, follow the instructions in the guide: Error: /opt/local/bin/port: port selfupdate failed: Error installing new Mac Ports base: command execution failed $ $ sudo port upgrade emacsapp Password: Warning: port definitions are more than two weeks old, consider updating them by running 'port selfupdate'.rsync: change_dir "tarballs/Port Index_darwin_13_i386" (in release) failed: No such file or directory (2) done sent 4 bytes received 9 bytes 26.00 bytes/sec total size is 0 speedup is 0.00 rsync error: some files could not be transferred (code 23) at /Source Cache/rsync/rsync-42/rsync/main.c(1400) [receiver=2.6.9] Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/Port Index_darwin_13_i386/Port Index /opt/local/var/macports/sources/rsync.macports.org/release/tarballs Exit code: 23 --- Mac Ports base is outdated, installing new version 2.2.1 Installing new Mac Ports release in /opt/local as root:admin; permissions 0755; Tcl-Package in /Library/Tcl checking build system type... The 2.2.1 installer for Mavericks has since become available here.x86_64-apple-darwin13.0.0 checking host system type... x86_64-apple-darwin13.0.0 checking target system type... x86_64-apple-darwin13.0.0 checking Mac Ports version... Make a list of your installed ports, and consider deleting I got an error with selfupdate, and resolved it by doing a fresh installation of Mac Ports from done sent 36 bytes received 70 bytes 70.67 bytes/sec total size is 57702400 speedup is 544362.26 receiving file list ... --- Updating the ports tree Synchronizing local ports tree from file:///opt/local/var/macports/sources/svn.macports.org/trunk/dports/ svn: E155036: Please see the 'svn upgrade' command svn: E155036: Working copy '/opt/local/var/macports/sources/svn.macports.org/trunk/dports' is too old (format 10, created by Subversion 1.6) Command failed: /usr/bin/svn update --non-interactive /opt/local/var/macports/sources/svn.macports.org/trunk/dports Exit code: 1 Error: Synchronization of the local ports tree failed doing an svn update Error: Couldn't sync the ports tree: Synchronization of 1 source(s) failed To report a bug, follow the instructions in the guide: Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the ports tree: Synchronization of 1 source(s) failed I answered a similar question.done sent 36 bytes received 77 bytes 75.33 bytes/sec total size is 512 speedup is 4.53 receiving file list ... The location of the Tcl framework has changed, breaking the existing Mac Ports infrastructure.This port must be manually opened on the VM for the incoming traffic, along with HTTP and HTTPS: Choose the Custom rule and enter the value of the SSH port that you set on Buddy.

The same applies for HTTP and HTTPS: if you've changed their default value on Buddy, add Custom rules and enter the ports manually.

UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=3 -e UNICORN_SIDEKIQS=1 -e RUBY_GC_MALLOC_LIMIT=40000000 -e RUBY_HEAP_MIN_SLOTS=800000 -e DISCOURSE_DB_SOCKET=/var/run/postgresql -e DISCOURSE_DB_HOST= -e DISCOURSE_DB_PORT= -e HOME=/root -e [email protected] -e DISCOURSE_HOSTNAME=discourse.-e DISCOURSE_SMTP_ADDRESS=1.99 -e DISCOURSE_SMTP_PORT=25 cd /pups && git pull && /pups/bin/pups --stdin From https://github.com/Sam Saffron/pups ee8fdfb..4203610 master - origin/master Updating ee8fdfb..4203610 Fast-forward | 10 - 1 file changed, 9 insertions( ), 1 deletion(-) I, [2015-04-03T.306027 #42] INFO -- : Loading --stdin I, [2015-04-03T.311509 #42] INFO -- : chown postgres:postgres /shared/postgres_run chown: changing ownership of ‘/shared/postgres_run’: Permission denied I, [2015-04-03T.316571 #42] INFO -- : FAILED -------------------- Runtime Error: chown postgres:postgres /shared/postgres_run failed with return # Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn' exec failed with the params "chown postgres:postgres /shared/postgres_run" 636e1e19598654f74f512c0640201409b23a24565f0f7b94256da4b6b32bd634 FAILED TO BOOTSTRAP Now that I think about it there is another change that is relevant.

Earlier this week I ran a yum update and I recall seeing Docker upgraded from 1.3.x to 1.5.0.

I don't know Docker well enough to know if that would matter.

If you want to run other websites on the same machine as Discourse, you need to set up an extra NGINX proxy in front of the Docker container.

I'm thinking that the rebuild is updating my instance to 1.3.0 beta4 which includes some updates to the Postgresql instance within the container. A script is calling a chown on /shared/postgres_run and chown is returning a permission denied error. I'm an experienced *nix admin, but very new to Docker and Discourse so I've had no luck fixing this myself.