Home » Network & Servers » Page 4

We are in a process of decomissioning a handfull of Fujitsu
Primergy Servers. Before of course, we want to make sure that the hard
disks are completely wiped out. But it seems there is no way to format
hard disks one by one as the RAID array controller is not detected by
utilites such as DBAN. I have already deleted and recreated RAID. My
question is, is that enough?



Some points to note:




  • These are leased servers, so physical destruction of the hard
    disks is not an option.


  • I have tried to configure JBOD for the controller, but seems it
    doesn't support it.


  • Latest Ubuntu, Debian, Gparted or DBAN don't recognize the
    controller or disks.


Currently I have my exim configuration set to send all e-mails
using an external SMTP server. All users authenticate with my exim
server with a local password and then the messages sent is relayed
through a smarthost to a remote SMTP server, which uses a different
login compared to the one used directly by the users connected to my
exim server (running cPanel). Here's the current configuration:



remote_route:
driver = manualroute
domains = !+local_domains
transport = remote_transport
route_list = * remotesmtpserver.com

remote_transport:
driver = smtp
port = 587
hosts_require_auth = <; $host_address
hosts_require_tls = <; $host_address

remote_login:
driver = plaintext
public_name = LOGIN
hide client_send = : remote_username : remote_password


This all works well and as intended.



The problem is that I want to use a different remote_username and
remote_password for a select group of users/senders. The login names
(for my exim server) are full e-mail addresses, so I have added these
e-mail addresses to a file /etc/differentlogin (i.e list of e-mail
addresses separated by a new line).



I then tried following setup in the remote_login section:



remote_login:
driver = plaintext
public_name = LOGIN
hide client_send =
${lookup{$authenticated_id}lsearch{/etc/differentlogin}{:
different_username : different_passsword}{: remote_username :
remote_password}


However this gives me the following EXIM error when attempting to
send e-mails:



  == to@address.com R=remote_route T=remote_transport defer
(-48): expansion of
"${lookup{$authenticated_id}lsearch{/etc/differentlogin}{" failed in
mandrill_login authenticator: missing } at end of string


I attempted using $sender_address instead of $authenticated_id, but
this gives me the same result.



I also tried replacing the variable to search for by a string
i.e:



remote_login:
driver = plaintext
public_name = LOGIN
hide client_send =
${lookup{email@domain.com}lsearch{/etc/differentlogin}{:
different_username : different_passsword}{: remote_username :
remote_password}


but I still get the same error.



To check the syntax of my conditional I tried to add the following
to my remote_transport:



headers_add = X-SenderTest:
${lookup{$authenticated_id}lsearch{/etc/differentlogin}{different}{normal}}


This works as expected and add the following header when sending an
e-mail from the addresses/logins noted in the list
/etc/differentlogin



X-SenderTest: different


Any tips?



Many thanks

since a few seconds I can not use htop or top in my
LXC-containers:




Cannot open /proc/stat: Transport endpoint is not connected




Same problem on reloading php5-fpm



Dez 18 13:40:31 systemd[1]: Failed to create cgroup
/lxc/103/system.slice/systemd-random-seed.service: Transport endpoint
is not connected

Dez 18 13:40:31 systemd[1]: Failed to realize cgroups for queued unit
systemd-random-seed.service: Transport endpoint is not connected

Dez 18 13:40:31 systemd[1]: Failed to create cgroup
/lxc/103/system.slice/networking.service: Transport endpoint is not
connected

Dez 18 13:40:31 systemd[1]: Failed to realize cgroups for queued unit
networking.service: Transport endpoint is not connected

Dez 18 13:40:31 systemd[1]: Failed to create cgroup
/lxc/103/system.slice/kbd.service: Transport endpoint is not connected

Dez 18 13:40:31 systemd[1]: Failed to realize cgroups for queued unit
kbd.service: Transport endpoint is not connected

Dez 18 13:40:31 systemd[1]: Failed to create cgroup
/lxc/103/system.slice/systemd-journald.service: Transport endpoint is
not connected

Dez 18 13:40:31 systemd[1]: Failed to realize cgroups for queued unit
systemd-journald.service: Transport endpoint is not connected

Dez 18 13:40:31 systemd[1]: php5-fpm.service: control process exited,
code=exited status=219

Dez 18 13:40:31 systemd[1]: Reload failed for The PHP FastCGI Process
Manager.


This is the syslog



Dec 18 13:41:13 systemd[30954]: Received SIGRTMIN+24 from
PID 30962 (kill).

Dec 18 13:42:13 systemd[31685]: Starting Paths.

Dec 18 13:42:13 systemd[31685]: Reached target Paths.

Dec 18 13:42:13 systemd[31685]: Starting Timers.

Dec 18 13:42:13 systemd[31685]: Reached target Timers.

Dec 18 13:42:13 systemd[31685]: Starting Sockets.

Dec 18 13:42:13 systemd[31685]: Reached target Sockets.

Dec 18 13:42:13 systemd[31685]: Starting Basic System.

Dec 18 13:42:13 systemd[31685]: Reached target Basic System.

Dec 18 13:42:13 systemd[31685]: Starting Default.

Dec 18 13:42:13 systemd[31685]: Reached target Default.

Dec 18 13:42:13 systemd[31685]: Startup finished in 5ms.

Dec 18 13:42:13 systemd[31685]: Stopping Default.

Dec 18 13:42:13 systemd[31685]: Stopped target Default.

Dec 18 13:42:13 systemd[31685]: Stopping Basic System.

Dec 18 13:42:13 systemd[31685]: Stopped target Basic System.

Dec 18 13:42:13 systemd[31685]: Stopping Paths.

Dec 18 13:42:13 systemd[31685]: Stopped target Paths.

Dec 18 13:42:13 systemd[31685]: Stopping Timers.

Dec 18 13:42:13 systemd[31685]: Stopped target Timers.

Dec 18 13:42:13 systemd[31685]: Stopping Sockets.

Dec 18 13:42:13 systemd[31685]: Stopped target Sockets.

Dec 18 13:42:13 systemd[31685]: Starting Shutdown.

Dec 18 13:42:13 systemd[31685]: Reached target Shutdown.

Dec 18 13:42:13 systemd[31685]: Starting Exit the Session...

Dec 18 13:42:13 systemd[31685]: Received SIGRTMIN+24 from PID 31693
(kill).

Dec 18 13:42:54 systemd-timesyncd[535]:
interval/delta/delay/jitter/drift 2048s/-0.000s/0.000s/0.003s/+3ppm

Dec 18 13:43:13 systemd[32540]: Starting Paths.

Dec 18 13:43:13 systemd[32540]: Reached target Paths.

Dec 18 13:43:13 systemd[32540]: Starting Timers.

Dec 18 13:43:13 systemd[32540]: Reached target Timers.

Dec 18 13:43:13 systemd[32540]: Starting Sockets.

Dec 18 13:43:13 systemd[32540]: Reached target Sockets.

Dec 18 13:43:13 systemd[32540]: Starting Basic System.

Dec 18 13:43:13 systemd[32540]: Reached target Basic System.

Dec 18 13:43:13 systemd[32540]: Starting Default.

Dec 18 13:43:13 systemd[32540]: Reached target Default.

Dec 18 13:43:13 systemd[32540]: Startup finished in 5ms.

Dec 18 13:43:13 systemd[32540]: Stopping Default.

Dec 18 13:43:13 systemd[32540]: Stopped target Default.

Dec 18 13:43:13 systemd[32540]: Stopping Basic System.

Dec 18 13:43:13 systemd[32540]: Stopped target Basic System.

Dec 18 13:43:13 systemd[32540]: Stopping Paths.

Dec 18 13:43:13 systemd[32540]: Stopped target Paths.

Dec 18 13:43:13 systemd[32540]: Stopping Timers.

Dec 18 13:43:13 systemd[32540]: Stopped target Timers.

Dec 18 13:43:13 systemd[32540]: Stopping Sockets.

Dec 18 13:43:13 systemd[32540]: Stopped target Sockets.

Dec 18 13:43:13 systemd[32540]: Starting Shutdown.

Dec 18 13:43:13 systemd[32540]: Reached target Shutdown.

Dec 18 13:43:13 systemd[32540]: Starting Exit the Session...

Dec 18 13:43:13 systemd[32540]: Received SIGRTMIN+24 from PID 32548
(kill).

Dec 18 13:43:27 kernel: [49158.991100] audit: type=1400
audit(1450442607.793:1547): apparmor="DENIED" operation="file_perm"
profile="lxc-container-default" name="private/trace" pid=26896
comm="qmgr" requested_mask="r" denied_mask="r" fsuid=105 ouid=0

Dec 18 13:43:27 kernel: [49158.991104] audit: type=1400
audit(1450442607.793:1548): apparmor="DENIED" operation="file_perm"
profile="lxc-container-default" name="private/trace" pid=26896
comm="qmgr" requested_mask="r" denied_mask="r" fsuid=105 ouid=0


This is my PVE version



proxmox-ve: 4.1-26 (running kernel: 4.2.6-1-pve)

pve-manager: 4.1-1 (running version: 4.1-1/2f9650d4)

pve-kernel-4.2.6-1-pve: 4.2.6-26

pve-kernel-2.6.32-43-pve: 2.6.32-166

pve-kernel-4.2.2-1-pve: 4.2.2-16

pve-kernel-2.6.32-26-pve: 2.6.32-114

pve-kernel-4.2.3-2-pve: 4.2.3-22

lvm2: 2.02.116-pve2

corosync-pve: 2.3.5-2

libqb0: 0.17.2-1

pve-cluster: 4.0-29

qemu-server: 4.0-41

pve-firmware: 1.1-7

libpve-common-perl: 4.0-41

libpve-access-control: 4.0-10

libpve-storage-perl: 4.0-38

pve-libspice-server1: 0.12.5-2

vncterm: 1.2-1

pve-qemu-kvm: 2.4-17

pve-container: 1.0-32

pve-firewall: 2.0-14

pve-ha-manager: 1.0-14

ksm-control-daemon: 1.2-1

glusterfs-client: 3.5.2-2+deb8u1

lxc-pve: 1.1.5-5

lxcfs: 0.13-pve1

cgmanager: 0.39-pve1

criu: 1.6.0-1


What can I do here?

I'm having an external spam filter scan our messages for SPAM.
However, if the message is borderline SPAM, I'd love for it to be
dropped into the user's "Junk Email" folder in Outlook/OWA.



I've setup the Antispam agents in Exchange 2013, but disabled most
of the components. I do however, have the org-wide SCLJunkTheshold
set to 4. I have a transport rule that is setting these borderline
messages' SCL to 5. However, they're not getting placed in the Junk
Email folder. I have verified in the headers that the SCL has been
set correctly. Any idea what else I should try?

I've setup SSL for a site of mine and while everything functions as
expected on desktop, I've noticed on some mobile devices the site
generates a "CA not trusted" error. On multiple SSL verification
utilities on the web, my configuration is reported as correct. I'm
trying to get SSL functioning correctly on these select mobile
devices.



I've spoken with my CA (Comodo) and they suggested the issue likely
has to do with my intermediate certificate (or lack of). Since I am
running on IBM i V7R2, no one over there was familiar with the process
to set up an intermediate certificate. I have searched online to
figure out how to set one up (or even if it is possible) but have had
no luck. This particular URL is what I followed while setting up the
SSL certificate, but it has no mention of setting up intermediate
certificates.



href="http://www-01.ibm.com/support/docview.wss?uid=nas8N1010356"
rel="nofollow">http://www-01.ibm.com/support/docview.wss?uid=nas8N1010356



There are plenty of resources online about setting up intermediate
certificates on LUW, but I have not even been able to find a reference
to such a thing on IBM i.



Has anyone done this before and could shed some insight? I feel
like I know what has to be done, but I just don't know how to do it
and information on the subject is scarce. I'm starting to think this
is not possible, but figured I'd put a question out to see if there
are any IBM i gurus who could confirm.



If there is any additional information which would be relevant,
please just ask.

I'm trying to set up a Load Balancer on Azure. I'm following href="https://azure.microsoft.com/en-us/documentation/articles/load-balancer-get-started-internet-arm-ps/#what-is-required-to-create-an-internet-facing-load-balancer"
rel="nofollow">this doc. At the end, you basically have to attach
your virtual network adapter to a running VM. The docs refer to using
Get-AzureRmVM to find the desired VM name in the desired
resource group. However, though I can see various VMs running on the
web portal, when I type:





Get-AzureRmVM





I don't get any results. However, if I type:





Get-AzureVM





I see all my virtual machines. The parameters are slightly
different, but it seems similar.



My Question:



What is the difference between Get-AzureRmVM and
Get-AzureVM? Why do all the docs say to use
Get-AzureRmVM when it doesn't appear to work?

I have a pfSense firewall that has a WAN with multiple public IP
addresses. I use NAT to port forward certain external IPs to internal
IPs.



I can connect from anywhere except same country. When anyone within
my country tries to connect to any external IP address and port, they
are unsuccessful. I've captured packets on the WAN interface and I see
them coming in.



I've double checked and there is indeed a WAN rule that allows the
accessed ports to NAT through to the servers that I intend them to. We
have no Geo IP checking or any IP address based rules to block traffic
to those servers.



-- I have noticed a difference between working connections and non
working connections



Using packet capture on pfSense (replaced some numbers with ###.###
which are the same numbers for all)



Non working connection:    
22:26:25.140803 IP 190.150.206.159.50852 > 190.###.###.2.80: tcp 0
22:26:25.140828 ARP, Request who-has 190.150.206.159 tell
190.###.###.3, length 28

Working Connection:
22:24:26.164293 IP 24.189.161.72.5550 > 190.###.###.2.80: tcp 0
22:24:26.164305 IP 190.###.###.2.80 > 24.189.161.72.5550: tcp 1460


Another connection from a pc on a different port to a different WAN
IP address (Same PFSense)



Non Working computer
09:39:05.612067 IP 190.87.162.111.2463 > 190.###.###.4.3389: tcp 0
09:39:08.610073 IP 190.87.162.111.2463 > 190.###.###.4.3389: tcp 0
09:39:14.608856 IP 190.87.162.111.2463 > 190.###.###.4.3389: tcp 0

Working Computer
09:41:04.412975 IP 68.196.25.71.60666 > 190.###.###.4.3389: tcp 85
09:41:04.459077 IP 190.###.###.4.3389 > 68.196.25.71.60666: tcp 0
09:41:04.492887 IP 68.196.25.71.60666 > 190.###.###.4.3389: tcp 101
09:41:04.537100 IP 190.###.###.4.3389 > 68.196.25.71.60666: tcp 0
09:41:06.177903 IP 190.###.###.4.3389 > 68.196.25.71.60666: tcp 101
09:41:06.309178 IP 68.196.25.71.60666 > 190.###.###.4.3389: tcp 0


I see in the Firewall that it is allowed but I cant figure out what
is blocking it.

src="http://i.stack.imgur.com/inDGW.png" alt="enter image description
here">



Would anyone happen to know how to resolve a
proc/8705/cmdline error?



I'm not even sure what that is but it's stopping my httpd client
from running.

I have bought a wild-card certificate for *.helloworld.com in
"Godaddy" and had tried to use it in "2.2.2.2" that is in digital
ocean which has my apache installed, ssl configured based on the above
certificate.



On trying to run the " rel="nofollow">https://2.2.2.2", i received the following
error:



"2.2.2.2" uses an invalid security certificate.

The certificate is only valid for the following names:
*.helloworld.com, helloworld.com

(Error code: ssl_error_bad_cert_domain)


To overcome this issue, i had tried to do a forward with masking in
"godaddy" for "x.helloworld.com" which is pointing to " href="https://2.2.2.2" rel="nofollow">https://2.2.2.2".



Still, i am facing the Error code: ssl_error_bad_cert_domain.



I am interested in having a clear understanding of my issue. Kindly
Someone help me by providing your views on this issue. Thanks in
advance.

I have one debian package source with md5sum file inside DEBIAN
directory



|-- DEBIAN
| |-- control
| |-- md5sums



  1. Now my question is when this file will be used?

  2. Will it be useful for integrity check of each file inside debian
    package before installing debian package?

  3. On machine when I install this debian package with manually
    modified md5sum(replaced some numbers in md5sum string) it doesn't
    show error, similar file is residing in
    /var/lib/dpkg/info/<package>.md5sums How can this
    be useful to check integrity of each file.


- Technology - Languages
+ Webmasters
+ Development
+ Development Tools
+ Internet
+ Mobile Programming
+ Linux
+ Unix
+ Apple
+ Ubuntu
+ Mobile & Tablets
+ Databases
+ Android
+ Network & Servers
+ Operating Systems
+ Coding
+ Design Software
+ Web Development
+ Game Development
+ Access
+ Excel
+ Web Design
+ Web Hosting
+ Web Site Reviews
+ Domain Name
+ Information Security
+ Software
+ Computers
+ Electronics
+ Hardware
+ Windows
+ PHP
+ ASP/ASP.Net
+ C/C++/C#
+ VB/VB.Net
+ JAVA
+ Javascript
+ Programming
Privacy Policy - Copyrights Notice - Feedback - Report Violation 2018 © BigHow