Why is this problem happening? Postfix Install Error - mta

The following error occurs during installation
Do you want to continue? [Y/n] y
Setting up postfix (3.6.4-1ubuntu1) ...
Postfix (main.cf) configuration was not changed. If you need to make changes,
edit /etc/postfix/main.cf (and others) as needed. To view Postfix
configuration values, see postconf(1).
After modifying main.cf, be sure to run 'systemctl reload postfix'.
Running newaliases
newaliases: warning: valid_hostname: numeric hostname: 8.8.4.4
newaliases: fatal: file /etc/postfix/main.cf: parameter mydomain: bad parameter value: 8.8.4.4
dpkg: error processing package postfix (--configure):
installed postfix package post-installation script subprocess returned error exit status 75
Errors were encountered while processing:
postfix
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
I reinstalled and restarted it.

Related

How to add trix.css when it is removed after pruning?

After pruning with the command "docker system prune -a" nodejs wont build anymore beacuse trix.css is missing. I am assuming this was probably deleted while pruning. How can I resolve this error (see the error below)? Why is it not created again while building the container again since the file is in the docker file.
Required path doesn't exist: /code/bower_components/trix/dist/trix.css trix
[13:57:39] 'vendorcss' errored after 1.63 ms
[13:57:39] Error: Promise rejected without Error
at Domain.onError (/usr/local/lib/node_modules/gulp/node_modules/async-done/index.js:49:15)
at Object.onceWrapper (events.js:315:30)
at emitOne (events.js:116:13)
at Domain.emit (events.js:211:7)
at Domain._errorHandler (domain.js:134:21)
at process._fatalException (bootstrap_node.js:375:33)
[13:57:39] 'staging' errored after 41 ms
ERROR: Service 'nodejs' failed to build: The command '/bin/sh -c gulp staging' returned a non-
zero code: 1
Usually I use this command : "sudo docker-compose -f docker-compose-staging.yml build nodejs" when I want to build the container again. I am very new to this and would be greatfull for some help.
For me, this was the case:
The issue exists because trix.css was removed in the latest version. It has nothing to do with docker system prune as far as I understand.
You can compare the two versions here: https://github.com/basecamp/trix/compare/1.3.1...v2.0.0
Basically, in order to fix this issue, you need to do
yarn install
yarn build
inside bower_components. This is suggested in the official updated README of the trix repository: https://github.com/basecamp/trix.
Once done with that, you will have trix.css and trix.umd.min.js files for your perusal.

Failed to build Dockerfile.devel with error -Werror=maybe-uninitialized

I am building tensorflow-server from source code, refer to doc, but it was failed.
My environment:
Linux 3.10.0-1062.12.1.el7.x86_64
Docker 19.03.8
Build command:
docker build --pull -t $USER/tensorflow-serving-devel -f tensorflow_serving/tools/docker/Dockerfile.devel
Error output:
ERROR: /root/.cache/bazel/_bazel_root/e53bbb0b0da4e26d24b415310219b953/external/upb/BUILD:57:1: C++ compilation of rule '#upb//:upb' failed (Exit 1)
external/upb/upb/table.c: In function 'upb_inttable_pop':
external/upb/upb/table.c:588:10: error: 'val.val' may be used uninitialized in this function [-Werror=maybe-uninitialized]
return val;
^~~
cc1: all warnings being treated as errors
Target //tensorflow_serving/model_servers:tensorflow_model_server failed to build
INFO: Elapsed time: 592.958s, Critical Path: 122.61s
INFO: 3550 processes: 3550 local.
FAILED: Build did NOT complete successfully
I've also faced this error when building latest version of Tensorflow Serving container. Looks like particular bazel version causes the error. I have found discussion under one of recent tensorflow serving updates - https://github.com/tensorflow/serving/commit/162f72949c6ecbe9e610182c923dec0aa5924cf2. I tried workaround suggested there, changing Tensorflow Serving branch from master to r2.1 by passing argument to docker build in such a way --build-arg TF_SERVING_VERSION_GIT_BRANCH=r2.1, it helped.

Debian9 - Upgrade virtaulbox fails on 'Cannot unload module vboxdrv.'

I'm trying to update debian 9 and virtualbox can't be upgrated...
I'm getting the error:
vboxdrv.sh: failed: Cannot unload module vboxdrv.
Does anybody has any idea ?
$ apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
virtualbox-5.1
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/66.9 MB of archives.
After this operation, 6,144 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 261193 files and directories currently installed.)
Preparing to unpack .../virtualbox-5.1_5.1.36-122089~Debian~stretch_amd64.deb ...
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
dpkg: error processing archive /var/cache/apt/archives/virtualbox-5.1_5.1.36-122089~Debian~stretch_amd64.deb (--unpack):
subprocess new pre-removal script returned error exit status 1
A copy of VirtualBox is currently running. Please close it and try again.
Please note that it can take up to ten seconds for VirtualBox to finish running.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /lib/systemd/system/vboxdrv.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /lib/systemd/system/vboxballoonctrl-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /lib/systemd/system/vboxautostart-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /lib/systemd/system/vboxweb-service.service.
vboxdrv.sh: failed: Cannot unload module vboxdrv.
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root.
Errors were encountered while processing:
/var/cache/apt/archives/virtualbox-5.1_5.1.36-122089~Debian~stretch_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Seen in the error messages you posted:
A copy of VirtualBox is currently running. Please close it and try again.
Please note that it can take up to ten seconds for VirtualBox to finish running.
Did you try that ?

{Yocto} "opkg_install_cmd: Cannot install package <package_name>." Errors

I am working with YOCTO project and running into the problem that made the build progress fail. The failure was at a last task do_rootfs
Below is the error log:
ERROR: Unable to install packages. Command '/home/yocto/Work/skrzg1h_iWg21m_QtHmi/build/tmp/sysroots/x86_64-linux/usr/bin/opkg-cl -f /home/yocto/Work/skrzg1h_iWg21m_QtHmi/build/tmp/work/iwg21m-poky-linux-gnueabi/core-image-weston/1.0-r0/opkg.conf -o /home/yocto/Work/skrzg1h_iWg21m_QtHmi/build/tmp/work/iwg21m-poky-linux-gnueabi/core-image-weston/1.0-r0/rootfs --force_postinstall --prefer-arch-to-version install locale-base-en-us locale-base-en-gb' returned 255:
Unknown package 'locale-base-en-us'.
Unknown package 'locale-base-en-gb'.
Collected errors:
* opkg_install_cmd: Cannot install package locale-base-en-us.
* opkg_install_cmd: Cannot install package locale-base-en-gb.
ERROR: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/yocto/Work/skrzg1h_iWg21m_QtHmi/build/tmp/work/iwg21m-poky-linux-gnueabi/core-image-weston/1.0-r0/temp/log.do_rootfs.31252
ERROR: Task 7 (/home/yocto/Work/skrzg1h_iWg21m_QtHmi/build/../poky/meta/recipes-graphics/images/core-image-weston.bb, do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5097 tasks of which 5096 didn't need to be rerun and 1 failed.
No currently running tasks (5096 of 5098)
Summary: 1 task failed:
/home/yocto/Work/skrzg1h_iWg21m_QtHmi/build/../poky/meta/recipes-graphics/images/core-image-weston.bb, do_rootfs
If you guys already run into this problem also, kindly support me how to fix this.
Thanks.

rabbitmq-plugins.bat enable rabbitmq_management

I install Erl7.3 and rabbitmq-server 3.6.2. I using Win7 32bit. After installing when I run 'rabbitmq-server' command it gives:
ERROR: node with name "rabbit" already running on "admin-PC"
When I run 'net stop RabbitMQ && net start RabbitMQ' it stopped RabbitMQ service and restarted successfully.
After that When I run "rabbitmq-plugins enable rabbitmq_management", it gives following errors and nothing is shown at http://localhost:15672:
Plugin configuration unchanged.
Applying plugin configuration to rabbit#admin-PC... failed.
Error: {undef,[{crypto,module_info,[attributes],[]},
{rabbit_misc,module_attributes,1,
[{file,"src/rabbit_misc.erl"},{line,817}]},
{rabbit_misc,'-all_module_attributes/1-fun-0-',3,
[{file,"src/rabbit_misc.erl"},{line,837}]},
{lists,foldl,3,[{file,"lists.erl"},{line,1262}]},
{rabbit_boot_steps,find_steps,1,
[{file,"src/rabbit_boot_steps.erl"},
{line,40}]},
{rabbit_boot_steps,run_boot_steps,1,
[{file,"src/rabbit_boot_steps.erl"},
{line,26}]},
{rabbit,start_apps,1,[{file,"src/rabbit.erl"},{line,451}]},
{rabbit_plugins,ensure,1,
[{file,"src/rabbit_plugins.erl"},{line,52}]}]}
For your information, I set environmental variables as:
'Variable name: ERLANG_HOME', 'Variable value: C:\Program Files\erl7.3';
'Variable name: RABBITMQ_SERVER', 'Variable value: C:\Program Files\RabbitMQ Server\rabbitmq_server-3.6.2'
and system path "%ERLANG_HOME%;;%RABBITMQ_SERVER%\sbin"
How to resolve this errors?
rabbitmq management plugin needs the cryptopakage to work.
see:
Error: {undef,[{crypto,module_info,[attributes],[]},
{rabbit_misc,module_attributes,1,
Try to use the Erlang 18.3 version.
EDIT
After installing when I run 'rabbitmq-server' command it gives:
ERROR: node with name "rabbit" already running on "admin-PC"
This is normal since rabbitmq-server starts the server, but you have rabbitmq installed and running as windows service.
And you should use the 64 bit version