Does anyone know of a good Postfix log file analysis program to find problems
with particular users?
In this instance I'm not interested in general statistics or anything. I just
want to do searches such as "all attempts for @gmail.com accounts to send mail
to user(a)example.com" where example.com is a local domain.
The native Postfix logging has one line with a sender address and queue ID and
later lines with the queue ID and the recipient(s) which may contain delivery
errors. So I can't just grep for the data I want.
My problem is when I get complains like "user(a)example.com can't receive mail
from friend(a)gmail.com". In many cases it's trivial problems that can be
difficult to diagnose, such as friend(a)gmail.com sending mail to
user2(a)example.com where user2 has just added the sender to the spam list and
not told anyone. So all parts of the server are working correctly but the
users aren't getting what they want.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
Just an update on the current situation..........
It looks like trying to compare i386 to AMD64 on this particular system is
a moot point at this stage as I cannot get the NVidia closed src driver to
work and the open src driver is __not__ satisfactory for 3D work. It being
quite slow and not doing the textures correctly.
The problem with the closed src driver is it causes the xserver to exit
just after start up due to a memory violation apparently in the pthread
library. This happens on all software configurations i have tried, Four
different kernels, two versions of Debian (7.2 and current Sid) and 3
differnt versions of the closed src driver. I have posted a bug report onan
Nvdia developers forum, there has been no reply as yet.
Nvidia docs do say there is somekind of known issue with the pthread
library causing crash's so I _MAY_ be suffeering from this.
I will have a think about this today, what I may do is to swap the video
card. I have a Radeon 2 gigabyte HD7870 spare currently and there are good
reports on the latest driver 3.11 beta and this is avaible for Sid. This
will save having to reinstall debian.
Hmmmmmmmmmmmmmm I may swap the GTX680 into a ASUS X58 MB, this being an
older known reliable gamming MB, as the 680 should be OK no reports of
problems can be found on the net.
Is'nt it a pain when hardware gives problems...........
Lindsay
My home Wifi network used to allow me to FTP files to my Android phones at rates
exceeding 1MB/s, I think that 1.9MB/s was my record. With that sort of speed
transferring a 200MB or 300MB TV show to a phone was reasonably quick.
Performance wasn't always great, sometimes it was as low as 400KB/s, but even
that was usable. In the past I had even watched TV shows on my phone over
HTTP (from a local server) with no performance problems. In the last few days
performance has dropped to below 60KB/s with rates like 40KB/s (that would be
320Kb/s) being common.
Because Android doesn't let me know what's happening I connected my Thinkpad
T420 via Wifi and saw the following result:
# iwconfig wlan0
wlan0 IEEE 802.11abgn ESSID:"abcdef"
Mode:Managed Frequency:2.412 GHz Access Point: AA:AA:AA:AA:AA:AA
Bit Rate=1 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality=70/70 Signal level=-30 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:286 Invalid misc:11 Missed beacon:0
What's going on here? I ran "iwconfig wlan0 rate auto" which made it briefly
claim a rate of "130 Mb/s" but then it reported 1Mb/s again. 1Mb/s rate for
the Wifi connection would be expected to give something like 40KB/s FTP
transfer speed so it seems that the phones are connecting in the same way as
my laptop.
It says that "abgn" is supported which should give lots of options for rates
higher than 1Mb/s, especially when the quality is 70/70 and the Wifi access
point (a Netgear DGN 2200 ADSL modem) is about 2M away from my laptop with
nothing of note in between.
Any suggestions for what I can do to improve performance?
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
During a recent discussion on i386 V AMD64 linux a number of people said
stay away from Physical Address Extension PAE kernels, althougth no
reasons/evidence was given to back up the warning, What is the problem with
PAE. A search on the net showed no major problems ascociated with this
extension apart from the obvious limited amount of memory avaible for a
single process.
As stated I have run PAE kernels now for some time with no problems what so
ever.
On Debian AMD64 I have managed to get wine running but as yet I cannot
compile wine itself, the build complaining of no 32 bit compiler (which is
correct). Sadly Debian sid will not let me install one without removing
alot of packages including xorg, this certainly not what I want.
A search on the net came up with a good bit of info on both running and
compiling wine on Debian AMD64 unfortunately none of it was recent and some
of the info conflicked.
So I am going to have a crack at Debian 7.0.0 i386 which I have a set of
DVD's for, having obtained them "just in case" .
If its required re intallation of Sid is a non issue with apt-move and
saving the package selections. Although there's one minor gripe apt-move
will store the AMD64 packages OK but will not handle the i386 items (on the
system for wine). The actual amount of data invloved is only around 100meg
so its not a real major issue.
Lindsay
Thanks for the reply, it is apreciated.
Russell Coker said,
> The limit on per-process address space (which isn't just a limit on memory
> use) is the main thing. Also there are performance issues with PAE.
The problem with claims of performance differences is that an awefull lot
of things can effect this and I have only seen one report (of 32 v 64 bit)
giving full details and test results of said tests. These showed some
things were faster and some were not. There are plenty of sites claiming
performance enhancements of 64 bit, almost none (only a single site) gives
any real evidence, most sites __clearly__ cherry picking data. This sort of
thing makes me __very__ sceptical as if something really is faster one will
see benchmarks published all over the place.
> Have you enabled multi-arch?
Yes, the last remaining problem is getting the closed src driver working
everything I have tried so far leads to the same thing. The X server
crashing after start up from a memory violation to do with a font library.
This is also with Debian Stable AND sid, four different kernels, two of
Debian's the others my own and of course two differnt vserions of xorg.
I am going to try i386 to see what will happen, I may add I have never had
the current graphics card an NVidia GTX 680 working on a closed src driver
under linux, works __mostly__ great under the open src driver. The card
works great under Windows XP.
Lindsay
Hello All,
I am using Opera 12.16 on Fedora 19 x86_64.
Recently Opera began to incorrectly render the page at
<https://groups.google.com/forum/#!forum/hugin-ptx>.
Here, it renders a lot of text, which looks like a lot like page source
code, in the top 3/4 of the page, and the normal forum posts right at the
bottom of the page.
I posted a question on the Opera forum, and it was suggested that I clear
the cache and restart Opera.
That actually worked...for a very short time, then it was back to the same
problem.
I have tried clearing the cache again, but it now has no effect.
The page renders OK on Firefox. I guess I could use Firefox, but would
prefer to keep on with Opera if I can.
Anyone have any ideas on how this might be fixed?
If it is of any help, I can capture a screen and post the image on Dropbox.
Cheers,
--
Regards,
Terry Duell
