Re: [CentOS] time zone

[Richard]

> Date: Tuesday, January 31, 2017 21:38:35 -0500
> From: TE Dukes 
> 
> 
> There have been no changes to the php.ini. Not sure how to output
> phpinfo to a text file for posting.
> 
> SystemLinux ts130.palmettodomains.com 3.10.0-514.6.1.el7.x86_64
> #1 SMP Wed Jan 18 13:06:36 UTC 2017 x86_64
> Build DateNov 6 2016 00:30:05
> Server APIApache 2.0 Handler
> Virtual Directory Support disabled
> Configuration File (php.ini) Path /etc
> Loaded Configuration File /etc/php.ini
> 
> date
> 
> Warning: phpinfo(): It is not safe to rely on the system's timezone
> settings. You are *required* to use the date.timezone setting or the
> date_default_timezone_set() function. In case you used any of those
> methods and you are still getting this warning, you most likely
> misspelled the timezone identifier. We selected the timezone 'UTC'
> for now, but please set date.timezone to select your timezone. in
> /var/www/html/phpinfo.php on line 4
> date/time support enabled
> "Olson" Timezone Database Version 0.system
> Timezone Database internal
> Default timezone  UTC
> 
> It is using UTC as the default time zone.
> 
> This could possibly be a bug in zoneminder. Not sure. Odd that
> after almost a week, this happens.
> 
> I have posted in their forum.
> 

The phpinfo() output has nothing to do with zoneminder, it's directly
reporting the php configuration being used by apache.

Where is the php.ini that showed the America/New_York value? What is
the last modified date/time on that file, compared to the last
[re]start of the httpd on that machine?

The "date.timezone" value can be set within a php script, and that
may be relevant to zoneminder, but the phpinfo() function is getting
the system-level settings -- which come from the php.ini that is
being loaded.

It is possible that you have .ini files in /etc/php.d. I doubt that
they would be overriding the php.ini's TZ setting, but you should
check.



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mail issues

[Peter]

On 01/02/17 15:51, TE Dukes wrote:
> Have been using mailscanner with postfix for years with no problems..

Suit yourself, you've been warned.

> I do believe it does not work with 7.3.  It does not start postfix as it did
> in 6.8 and earlier versions. There may be other problems besides that as
> well. 
> 
> Figured out it wasn't a firewall issue when I would telnet to localhost 25
> and got connection refused. As soon as I started postfix manually, I could
> connect.
> 
> Mail works now that it has been uninstalled and adding a few things from
> last night that were posted.

your log from earlier showed it working, it would normally be delivered
to the default location of /var/mail.

You asked how to get it to show up in ~/Maildir.  That requires you set
the home_mailbox setting as I previously stated.


Peter
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mail issues

[TE Dukes]

> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Peter
> Sent: Tuesday, January 31, 2017 8:40 PM
> To: centos@centos.org
> Subject: Re: [CentOS] Mail issues
> 
> On 31/01/17 12:50, TE Dukes wrote:
> > This is a fresh install of dovecot and postfix. I have uninstalled
> > mailscanner as well until I can figure out what's wrong.
> 
> You shouldn't use mailscanner anyways, it relys on direct manipulation of
the
> postfix queue files which is unsupported by postfix.  Consider amavisd-new
> and spamassassin/clamav instead.
> 
> > I sent a test mail from root to tdukes but its not being delivered to
> > ~/Maildir
> 
> as I said in another post, you need to set:
> 
> home_mailbox = Maildir/
> 
> ...in main.cf.  Note that the trailing slash means it will be delivered in
maildir
> format (which is likely what you want), if you would rather that local(8)
> deliver in mbox format then omit the trailing slash.
> 
> 

Have been using mailscanner with postfix for years with no problems..

I do believe it does not work with 7.3.  It does not start postfix as it did
in 6.8 and earlier versions. There may be other problems besides that as
well. 

Figured out it wasn't a firewall issue when I would telnet to localhost 25
and got connection refused. As soon as I started postfix manually, I could
connect.

Mail works now that it has been uninstalled and adding a few things from
last night that were posted.

I have setup clamav and spamassassin using this guide.

http://www.tecmint.com/integrate-clamav-and-spamassassin-to-protect-postfix-
mails-from-viruses/

Seems to work.



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] time zone

[TE Dukes]

> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard
> Sent: Tuesday, January 31, 2017 7:52 PM
> To: CentOS mailing list
> Subject: Re: [CentOS] time zone
> 
> 
> 
> > Date: Tuesday, January 31, 2017 19:35:46 -0500
> > From: TE Dukes 
> >
> >> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard
> >> Sent: Tuesday, January 31, 2017 6:46 PM
> >>
> >> > Date: Tuesday, January 31, 2017 18:16:36 -0500
> >> > From: TE Dukes 
> >> >
> >> >> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
> >> >> Richard Sent: Tuesday, January 31, 2017 5:19 PM
> >> >>
> >> >>
> >> >> > Date: Tuesday, January 31, 2017 16:59:32 -0500
> >> >> > From: TE Dukes 
> >> >>
> >> >> >
> >> >> > From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
> >> >> > Richard Sent: Tuesday, January 31, 2017 4:44 PM
> >> >>
> >> >> >
> >> >> >> Date: Tuesday, January 31, 2017 16:02:37 -0500
> >> >> >> From: TE Dukes 
> >> >> >>
> >> >> >> Today, I started getting this error when trying to login to
> >> >> >> zoneminder:
> >> >> >>
> >> >> >> ZoneMinder is not installed properly: php's date.timezone is
> >> >> >> not set to a valid timezone
> >> >> >>
> >> >> >> Zoneminder has been running since last Wednesday when I
> >> >> >> installed it. Today, I get this.
> >> >> >>
> >> >> >> In /etc/php.ini, I have date.timezone = America/New_York, which
> >> >> >> I added when zoneminder was installed.
> >> >> >>
> >> >> >> Output from date: Tue Jan 31 15:56:26 EST 2017
> >> >> >>
> >> >> >> Output from ll /etc/localtime: lrwxrwxrwx. 1 root root 38 Jan
> >> >> >> 25 19:05 /etc/localtime ->
> >> >> >> ../usr/share/zoneinfo/America/New_York
> >> >> >>
> >> >> >> Been searching for hours for another file that may be
> >> >> >> overriding php.ini
> >> >> >>
> >> >> >
> >> >> > Put a simple php page on your/the server (where zoneminder is
> >> >> > running) with the "phpinfo()" function, and then look at the
> >> >> > timezone information in the "date" section of the output.
> >> >> >
> >> >> > If it isn't showing the correct value, check the location of the
> >> >> > php.ini that is being used in the "Loaded Configuration File"
> >> >> > value toward the top of that output.
> >> >> >
> >> >> > By default, php doesn't use the system's TZ,
> >> >> >
> >> >> >
> >> >> > Hello,
> >> >> >
> >> >> > I did, it shows the error about not being correctly set:
> >> >> >
> >> >> > Warning: phpinfo(): It is not safe to rely on the system's
> >> >> > timezone settings. You are *required* to use the date.timezone
> >> >> > setting or the date_default_timezone_set() function. In case you
> >> >> > used any of those methods and you are still getting this
> >> >> > warning, you most likely misspelled the timezone identifier. We
> >> >> > selected the timezone 'UTC' for now, but please set
> >> >> > date.timezone to select your timezone. in
> >> >> > /var/www/html/phpinfo.php on line 4
> >> >> >
> >> >> > Why would it just start doing this?
> >> >> >
> >> >>
> >> >> Obviously can't answer that as we don't know enough about what
> >> >> changes you may have made to your system. The default php.ini
> >> >> doesn't have a TZ set, so will always give that message
> >> >> unless/until you add a TZ.
> >> >>
> >> >> However, to fix this:
> >> >>
> >> >>   - check the location of the php.ini that is being referenced,
> >> >> as indicated above (generally /etc/php.ini).
> >> >>
> >> >>   - edit that php.ini file to set a correct TZ following the
> >> >> "date.timezone =" entry.
> >> >>
> >> >>   - be certain to uncomment that line.
> >> >>
> >> >>   - you probably need to restart the apache server to get any
> >> >> change picked up.
> >> >>
> >> >
> >> > [Date]
> >> > ; Defines the default timezone used by the date functions ;
> >> > http://php.net/date.timezone date.timezone = America/New_York
> >> >
> >> > Its set. Not sure why its not seeing it. The only changes I made to
> >> > php.ini was this last week when I installed 7.3 and zoneminder.
> >> >
> >> > Its been working up till about noon today.
> >> >
> >>
> >> You need to make certain that the php.ini where you have that setting
> >> is
> > the
> >> one that is being referenced by the server. See above notes on
> >> checking that.
> >>
> >> The apache server needs to be restarted to load changes made to the
> >> php.ini.
> >>
> >> These things don't change "magically". If this worked until noon, I'd
> > check
> >> various logs to see who/what made changes then - including looking to
> >> see
> > if
> >> the apache server was restarted then and loaded changes made
> >> previously.
> >>
> >>
> >
> > Here's an excerpt from /var/log/messages:
> >
> > Jan 31 12:15:19 ts130 zmc_dvideo0[13838]: INF [Den: 57000 - Capturing
> > at 29.41 fps] Jan 31 12:15:19 ts130 zmc_dvideo1[13864]: INF [Deck:
> > 57000 - Capturing at 30.30 fps] Jan 31 

Re: [CentOS] Mail issues

[Peter]

On 31/01/17 12:50, TE Dukes wrote:
> This is a fresh install of dovecot and postfix. I have uninstalled
> mailscanner as well until I can figure out what's wrong.

You shouldn't use mailscanner anyways, it relys on direct manipulation
of the postfix queue files which is unsupported by postfix.  Consider
amavisd-new and spamassassin/clamav instead.

> I sent a test mail from root to tdukes but its not being delivered to
> ~/Maildir

as I said in another post, you need to set:

home_mailbox = Maildir/

...in main.cf.  Note that the trailing slash means it will be delivered
in maildir format (which is likely what you want), if you would rather
that local(8) deliver in mbox format then omit the trailing slash.


Peter
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mail issues

[Peter]

On 31/01/17 13:36, John R Pierce wrote:
> On 1/30/2017 4:13 PM, TE Dukes wrote:
>> This is a fresh install, I haven't changed anything except adding
>> mail_location = maildir:~/Maildir in /etc/dovecot/conf.d/10-mail.conf
> 
> the mail transfer agent (postfix) needs a mail delivery agent for
> locally delivered mail, in traditional email systems this was often
> procmail or fetchmail. dovecot is a mail client, although it contains an
> optional local delivery agent.  a bit of googling found
> http://wiki.dovecot.org/LDA/Postfix

This is incorrect.  Postfix comes with it's own lda (local(8)) which
fills this role.  It is true that it can use a 3rd party lda but it is
not necessary.

To the OP:

Set: "home_mailbox = Maildir/" in main.cf.


Peter
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] time zone

[Richard]

> Date: Tuesday, January 31, 2017 19:35:46 -0500
> From: TE Dukes 
> 
>> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
>> Richard Sent: Tuesday, January 31, 2017 6:46 PM
>> 
>> > Date: Tuesday, January 31, 2017 18:16:36 -0500
>> > From: TE Dukes 
>> > 
>> >> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
>> >> Richard Sent: Tuesday, January 31, 2017 5:19 PM
>> >> 
>> >> 
>> >> > Date: Tuesday, January 31, 2017 16:59:32 -0500
>> >> > From: TE Dukes 
>> >> 
>> >> > 
>> >> > From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
>> >> > Richard Sent: Tuesday, January 31, 2017 4:44 PM
>> >> 
>> >> > 
>> >> >> Date: Tuesday, January 31, 2017 16:02:37 -0500
>> >> >> From: TE Dukes 
>> >> >> 
>> >> >> Today, I started getting this error when trying to login to
>> >> >> zoneminder:
>> >> >> 
>> >> >> ZoneMinder is not installed properly: php's date.timezone is
>> >> >> not set to a valid timezone
>> >> >> 
>> >> >> Zoneminder has been running since last Wednesday when I
>> >> >> installed it. Today, I get this.
>> >> >> 
>> >> >> In /etc/php.ini, I have date.timezone = America/New_York,
>> >> >> which I added when zoneminder was installed.
>> >> >> 
>> >> >> Output from date: Tue Jan 31 15:56:26 EST 2017
>> >> >> 
>> >> >> Output from ll /etc/localtime: lrwxrwxrwx. 1 root root 38
>> >> >> Jan 25 19:05 /etc/localtime ->
>> >> >> ../usr/share/zoneinfo/America/New_York
>> >> >> 
>> >> >> Been searching for hours for another file that may be
>> >> >> overriding php.ini
>> >> >> 
>> >> > 
>> >> > Put a simple php page on your/the server (where zoneminder is
>> >> > running) with the "phpinfo()" function, and then look at the
>> >> > timezone information in the "date" section of the output.
>> >> > 
>> >> > If it isn't showing the correct value, check the location of
>> >> > the php.ini that is being used in the "Loaded Configuration
>> >> > File" value toward the top of that output.
>> >> > 
>> >> > By default, php doesn't use the system's TZ,
>> >> > 
>> >> > 
>> >> > Hello,
>> >> > 
>> >> > I did, it shows the error about not being correctly set:
>> >> > 
>> >> > Warning: phpinfo(): It is not safe to rely on the system's
>> >> > timezone settings. You are *required* to use the
>> >> > date.timezone setting or the date_default_timezone_set()
>> >> > function. In case you used any of those methods and you are
>> >> > still getting this warning, you most likely misspelled the
>> >> > timezone identifier. We selected the timezone 'UTC' for now,
>> >> > but please set date.timezone to select your timezone. in
>> >> > /var/www/html/phpinfo.php on line 4
>> >> > 
>> >> > Why would it just start doing this?
>> >> > 
>> >> 
>> >> Obviously can't answer that as we don't know enough about what
>> >> changes you may have made to your system. The default php.ini
>> >> doesn't have a TZ set, so will always give that message
>> >> unless/until you add a TZ.
>> >> 
>> >> However, to fix this:
>> >> 
>> >>   - check the location of the php.ini that is being referenced,
>> >> as indicated above (generally /etc/php.ini).
>> >> 
>> >>   - edit that php.ini file to set a correct TZ following the
>> >> "date.timezone =" entry.
>> >> 
>> >>   - be certain to uncomment that line.
>> >> 
>> >>   - you probably need to restart the apache server to get any
>> >> change picked up.
>> >> 
>> > 
>> > [Date]
>> > ; Defines the default timezone used by the date functions ;
>> > http://php.net/date.timezone date.timezone = America/New_York
>> > 
>> > Its set. Not sure why its not seeing it. The only changes I made
>> > to php.ini was this last week when I installed 7.3 and
>> > zoneminder.
>> > 
>> > Its been working up till about noon today.
>> > 
>> 
>> You need to make certain that the php.ini where you have that
>> setting is
> the
>> one that is being referenced by the server. See above notes on
>> checking that.
>> 
>> The apache server needs to be restarted to load changes made to the
>> php.ini.
>> 
>> These things don't change "magically". If this worked until noon,
>> I'd
> check
>> various logs to see who/what made changes then - including looking
>> to see
> if
>> the apache server was restarted then and loaded changes made
>> previously.
>> 
>> 
> 
> Here's an excerpt from /var/log/messages:
> 
> Jan 31 12:15:19 ts130 zmc_dvideo0[13838]: INF [Den: 57000 -
> Capturing at 29.41 fps]
> Jan 31 12:15:19 ts130 zmc_dvideo1[13864]: INF [Deck: 57000 -
> Capturing at 30.30 fps]
> Jan 31 12:15:19 ts130 zmc_dvideo2[13890]: INF [Front: 57000 -
> Capturing at 30.30 fps]
> Jan 31 12:15:19 ts130 zma_m1[13847]: INF [Den: 57000 - Analysing at
> 30.30 fps]
> Jan 31 12:15:20 ts130 zmc_dvideo3[13917]: INF [Street: 57000 -
> Capturing at 29.41 fps]
> Jan 31 12:15:20 ts130 zma_m2[13873]: INF [Deck: 57000 - Analysing
> at 29.41 fps]
> Jan 31 12:15:20 ts130 zma_m3[13899]: INF [Front: 57000 - Analysing

Re: [CentOS] time zone

[TE Dukes]

> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard
> Sent: Tuesday, January 31, 2017 6:46 PM
> To: CentOS mailing list
> Subject: Re: [CentOS] time zone
> 
> 
> 
> > Date: Tuesday, January 31, 2017 18:16:36 -0500
> > From: TE Dukes 
> >
> >> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard
> >> Sent: Tuesday, January 31, 2017 5:19 PM
> >>
> >>
> >> > Date: Tuesday, January 31, 2017 16:59:32 -0500
> >> > From: TE Dukes 
> >>
> >> >
> >> > From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
> >> > Richard Sent: Tuesday, January 31, 2017 4:44 PM
> >>
> >> >
> >> >> Date: Tuesday, January 31, 2017 16:02:37 -0500
> >> >> From: TE Dukes 
> >> >>
> >> >> Today, I started getting this error when trying to login to
> >> >> zoneminder:
> >> >>
> >> >> ZoneMinder is not installed properly: php's date.timezone is not
> >> >> set to a valid timezone
> >> >>
> >> >> Zoneminder has been running since last Wednesday when I installed
> >> >> it. Today, I get this.
> >> >>
> >> >> In /etc/php.ini, I have date.timezone = America/New_York, which I
> >> >> added when zoneminder was installed.
> >> >>
> >> >> Output from date: Tue Jan 31 15:56:26 EST 2017
> >> >>
> >> >> Output from ll /etc/localtime: lrwxrwxrwx. 1 root root 38 Jan 25
> >> >> 19:05 /etc/localtime -> ../usr/share/zoneinfo/America/New_York
> >> >>
> >> >> Been searching for hours for another file that may be overriding
> >> >> php.ini
> >> >>
> >> >
> >> > Put a simple php page on your/the server (where zoneminder is
> >> > running) with the "phpinfo()" function, and then look at the
> >> > timezone information in the "date" section of the output.
> >> >
> >> > If it isn't showing the correct value, check the location of the
> >> > php.ini that is being used in the "Loaded Configuration File"
> >> > value toward the top of that output.
> >> >
> >> > By default, php doesn't use the system's TZ,
> >> >
> >> >
> >> > Hello,
> >> >
> >> > I did, it shows the error about not being correctly set:
> >> >
> >> > Warning: phpinfo(): It is not safe to rely on the system's timezone
> >> > settings. You are *required* to use the date.timezone setting or
> >> > the date_default_timezone_set() function. In case you used any of
> >> > those methods and you are still getting this warning, you most
> >> > likely misspelled the timezone identifier. We selected the timezone
> >> > 'UTC' for now, but please set date.timezone to select your
> >> > timezone. in /var/www/html/phpinfo.php on line 4
> >> >
> >> > Why would it just start doing this?
> >> >
> >>
> >> Obviously can't answer that as we don't know enough about what
> >> changes you may have made to your system. The default php.ini doesn't
> >> have a TZ set, so will always give that message unless/until you add
> >> a TZ.
> >>
> >> However, to fix this:
> >>
> >>   - check the location of the php.ini that is being referenced,
> >> as indicated above (generally /etc/php.ini).
> >>
> >>   - edit that php.ini file to set a correct TZ following the
> >> "date.timezone =" entry.
> >>
> >>   - be certain to uncomment that line.
> >>
> >>   - you probably need to restart the apache server to get any
> >> change picked up.
> >>
> >
> > [Date]
> > ; Defines the default timezone used by the date functions ;
> > http://php.net/date.timezone date.timezone = America/New_York
> >
> > Its set. Not sure why its not seeing it. The only changes I made to
> > php.ini was this last week when I installed 7.3 and zoneminder.
> >
> > Its been working up till about noon today.
> >
> 
> You need to make certain that the php.ini where you have that setting is
the
> one that is being referenced by the server. See above notes on checking
> that.
> 
> The apache server needs to be restarted to load changes made to the
> php.ini.
> 
> These things don't change "magically". If this worked until noon, I'd
check
> various logs to see who/what made changes then - including looking to see
if
> the apache server was restarted then and loaded changes made previously.
> 
> 

Here's an excerpt from /var/log/messages:

Jan 31 12:15:19 ts130 zmc_dvideo0[13838]: INF [Den: 57000 - Capturing at
29.41 fps]
Jan 31 12:15:19 ts130 zmc_dvideo1[13864]: INF [Deck: 57000 - Capturing at
30.30 fps]
Jan 31 12:15:19 ts130 zmc_dvideo2[13890]: INF [Front: 57000 - Capturing at
30.30 fps]
Jan 31 12:15:19 ts130 zma_m1[13847]: INF [Den: 57000 - Analysing at 30.30
fps]
Jan 31 12:15:20 ts130 zmc_dvideo3[13917]: INF [Street: 57000 - Capturing at
29.41 fps]
Jan 31 12:15:20 ts130 zma_m2[13873]: INF [Deck: 57000 - Analysing at 29.41
fps]
Jan 31 12:15:20 ts130 zma_m3[13899]: INF [Front: 57000 - Analysing at 29.41
fps]
Jan 31 12:15:20 ts130 zma_m4[13925]: INF [Street: 57000 - Analysing at 30.30
fps]
Jan 31 12:15:41 ts130 web_php[15770]: FAT [ZoneMinder is not installed
properly: php's date.timezone is not set to a valid 

Re: [CentOS] time zone

[Richard]

> Date: Tuesday, January 31, 2017 18:16:36 -0500
> From: TE Dukes 
> 
>> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
>> Richard Sent: Tuesday, January 31, 2017 5:19 PM
>> 
>>
>> > Date: Tuesday, January 31, 2017 16:59:32 -0500
>> > From: TE Dukes 
>> 
>> > 
>> > From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
>> > Richard Sent: Tuesday, January 31, 2017 4:44 PM
>> 
>> > 
>> >> Date: Tuesday, January 31, 2017 16:02:37 -0500
>> >> From: TE Dukes 
>> >> 
>> >> Today, I started getting this error when trying to login to
>> >> zoneminder:
>> >> 
>> >> ZoneMinder is not installed properly: php's date.timezone is
>> >> not set to a valid timezone
>> >> 
>> >> Zoneminder has been running since last Wednesday when I
>> >> installed it. Today, I get this.
>> >> 
>> >> In /etc/php.ini, I have date.timezone = America/New_York, which
>> >> I added when zoneminder was installed.
>> >> 
>> >> Output from date: Tue Jan 31 15:56:26 EST 2017
>> >> 
>> >> Output from ll /etc/localtime: lrwxrwxrwx. 1 root root 38 Jan 25
>> >> 19:05 /etc/localtime -> ../usr/share/zoneinfo/America/New_York
>> >> 
>> >> Been searching for hours for another file that may be overriding
>> >> php.ini
>> >> 
>> > 
>> > Put a simple php page on your/the server (where zoneminder is
>> > running) with the "phpinfo()" function, and then look at the
>> > timezone information in the "date" section of the output.
>> > 
>> > If it isn't showing the correct value, check the location of the
>> > php.ini that is being used in the "Loaded Configuration File"
>> > value toward the top of that output.
>> > 
>> > By default, php doesn't use the system's TZ,
>> > 
>> > 
>> > Hello,
>> > 
>> > I did, it shows the error about not being correctly set:
>> > 
>> > Warning: phpinfo(): It is not safe to rely on the system's
>> > timezone settings. You are *required* to use the date.timezone
>> > setting or the date_default_timezone_set() function. In case you
>> > used any of those methods and you are still getting this
>> > warning, you most likely misspelled the timezone identifier. We
>> > selected the timezone 'UTC' for now, but please set
>> > date.timezone to select your timezone. in
>> > /var/www/html/phpinfo.php on line 4
>> > 
>> > Why would it just start doing this?
>> > 
>> 
>> Obviously can't answer that as we don't know enough about what
>> changes you may have made to your system. The default php.ini
>> doesn't have a TZ set, so will always give that message
>> unless/until you add a TZ.
>> 
>> However, to fix this:
>> 
>>   - check the location of the php.ini that is being referenced,
>> as indicated above (generally /etc/php.ini).
>> 
>>   - edit that php.ini file to set a correct TZ following the
>> "date.timezone =" entry.
>> 
>>   - be certain to uncomment that line.
>> 
>>   - you probably need to restart the apache server to get any
>> change picked up.
>> 
> 
> [Date]
> ; Defines the default timezone used by the date functions
> ; http://php.net/date.timezone
> date.timezone = America/New_York
> 
> Its set. Not sure why its not seeing it. The only changes I made to
> php.ini was this last week when I installed 7.3 and zoneminder.
> 
> Its been working up till about noon today.
> 

You need to make certain that the php.ini where you have that setting
is the one that is being referenced by the server. See above notes on
checking that.

The apache server needs to be restarted to load changes made to the
php.ini.

These things don't change "magically". If this worked until noon, I'd
check various logs to see who/what made changes then - including
looking to see if the apache server was restarted then and loaded
changes made previously.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] time zone

[TE Dukes]

> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard
> Sent: Tuesday, January 31, 2017 5:19 PM
> To: CentOS mailing list
> Subject: Re: [CentOS] time zone
> 
> 
> 
> > Date: Tuesday, January 31, 2017 16:59:32 -0500
> > From: TE Dukes 
> 
> >
> > From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard
> > Sent: Tuesday, January 31, 2017 4:44 PM
> 
> >
> >> Date: Tuesday, January 31, 2017 16:02:37 -0500
> >> From: TE Dukes 
> >>
> >> Today, I started getting this error when trying to login to
> >> zoneminder:
> >>
> >> ZoneMinder is not installed properly: php's date.timezone is not set
> >> to a valid timezone
> >>
> >> Zoneminder has been running since last Wednesday when I installed it.
> >> Today, I get this.
> >>
> >> In /etc/php.ini, I have date.timezone = America/New_York, which I
> >> added when zoneminder was installed.
> >>
> >> Output from date: Tue Jan 31 15:56:26 EST 2017
> >>
> >> Output from ll /etc/localtime: lrwxrwxrwx. 1 root root 38 Jan 25
> >> 19:05 /etc/localtime -> ../usr/share/zoneinfo/America/New_York
> >>
> >> Been searching for hours for another file that may be overriding
> >> php.ini
> >>
> >
> > Put a simple php page on your/the server (where zoneminder is
> > running) with the "phpinfo()" function, and then look at the timezone
> > information in the "date" section of the output.
> >
> > If it isn't showing the correct value, check the location of the
> > php.ini that is being used in the "Loaded Configuration File" value
> > toward the top of that output.
> >
> > By default, php doesn't use the system's TZ,
> >
> >
> > Hello,
> >
> > I did, it shows the error about not being correctly set:
> >
> > Warning: phpinfo(): It is not safe to rely on the system's timezone
> > settings. You are *required* to use the date.timezone setting or the
> > date_default_timezone_set() function. In case you used any of those
> > methods and you are still getting this warning, you most likely
> > misspelled the timezone identifier. We selected the timezone 'UTC'
> > for now, but please set date.timezone to select your timezone. in
> > /var/www/html/phpinfo.php on line 4
> >
> > Why would it just start doing this?
> >
> 
> Obviously can't answer that as we don't know enough about what changes
> you may have made to your system. The default php.ini doesn't have a TZ
> set, so will always give that message unless/until you add a TZ.
> 
> However, to fix this:
> 
>   - check the location of the php.ini that is being referenced,
> as indicated above (generally /etc/php.ini).
> 
>   - edit that php.ini file to set a correct TZ following the
> "date.timezone =" entry.
> 
>   - be certain to uncomment that line.
> 
>   - you probably need to restart the apache server to get any
> change picked up.
> 

[Date]
; Defines the default timezone used by the date functions
; http://php.net/date.timezone
date.timezone = America/New_York

Its set. Not sure why its not seeing it. The only changes I made to php.ini
was this last week when I installed 7.3 and zoneminder.

Its been working up till about noon today.

Thanks

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] time zone

[Richard]

> Date: Tuesday, January 31, 2017 16:59:32 -0500
> From: TE Dukes 

> 
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard
> Sent: Tuesday, January 31, 2017 4:44 PM

> 
>> Date: Tuesday, January 31, 2017 16:02:37 -0500
>> From: TE Dukes 
>> 
>> Today, I started getting this error when trying to login to
>> zoneminder:
>> 
>> ZoneMinder is not installed properly: php's date.timezone is not
>> set  to a valid timezone
>> 
>> Zoneminder has been running since last Wednesday when I installed
>> it.  Today, I get this.
>> 
>> In /etc/php.ini, I have date.timezone = America/New_York, which I 
>> added when zoneminder was installed.
>> 
>> Output from date: Tue Jan 31 15:56:26 EST 2017
>> 
>> Output from ll /etc/localtime: lrwxrwxrwx. 1 root root 38 Jan 25
>> 19:05 /etc/localtime -> ../usr/share/zoneinfo/America/New_York
>>  
>> Been searching for hours for another file that may be overriding 
>> php.ini
>> 
> 
> Put a simple php page on your/the server (where zoneminder is
> running) with the "phpinfo()" function, and then look at the
> timezone information in the "date" section of the output. 
> 
> If it isn't showing the correct value, check the location of the
> php.ini that is being used in the "Loaded Configuration File" value
> toward the top of that output.
> 
> By default, php doesn't use the system's TZ,
> 
> 
> Hello,
> 
> I did, it shows the error about not being correctly set:
> 
> Warning: phpinfo(): It is not safe to rely on the system's timezone
> settings. You are *required* to use the date.timezone setting or the
> date_default_timezone_set() function. In case you used any of those
> methods and you are still getting this warning, you most likely
> misspelled the timezone identifier. We selected the timezone 'UTC'
> for now, but please set date.timezone to select your timezone. in
> /var/www/html/phpinfo.php on line 4
> 
> Why would it just start doing this?
> 

Obviously can't answer that as we don't know enough about what
changes you may have made to your system. The default php.ini doesn't
have a TZ set, so will always give that message unless/until you add
a TZ.

However, to fix this:

  - check the location of the php.ini that is being referenced,
as indicated above (generally /etc/php.ini).

  - edit that php.ini file to set a correct TZ following the
"date.timezone =" entry.

  - be certain to uncomment that line.

  - you probably need to restart the apache server to get any
change picked up.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] NIC Stability Problems Under Xen 4.4 / CentOS 6 / Linux 3.18

[Adi Pircalabu]

On 31/01/17 21:00, Jinesh Choksi wrote:

On 30 January 2017 at 22:17, Adi Pircalabu wrote:

May I chip in here? In our environment we're randomly seeing:

Jan 17 23:40:14 xen01 kernel: ixgbe :04:00.1 eth6: Detected Tx
Unit Hang


Someone in this thread: https://sourceforge.net/p/e1000/bugs/530/#2855 
  reported that /"With these kernels I was only able to work around the 
issue by disabling tx-checksumming offload with ethtool."/


However, that was reported for Kernels 4.2.6 / 4.2.8 / 4.4.8 and 4.4.10. 
I just thought it could be something you could rule out and hence 
mentioned it:


ethtool --offload eth6 rx off tx off


Another thing to rule out in case its a regression with Intel NICs and TSO:

# tso => tcp-segmentation-offload
# gso => generic-segmentation-offload
# gro => generic-receive-offload
# sg => scatter-gather
# ufo => udp-fragmentation-offload (Cannot change)
# lro => large-receive-offload (Cannot change)

ethtool -K eth6 tso off gso off gro off sg off


Nice, useful information. I've just disabled tx & rx checksumming on all 
the 10Gb interfaces on the affected servers, see how it goes. But as I 
said yesterday, in our environment it takes months to replicate.


Thanks,

Adi Pircalabu
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] multipath show config different in CentOS 7?

[Alexander Dalloz]

Am 31.01.2017 um 22:51 schrieb Gianluca Cecchi:

Hello,
suppose I want to use a special configuration for my IBM/1814 storage array
luns, then I put something like this in multipath.conf

devices {
device {
vendor "IBM"
product "^1814"
product_blacklist "Universal Xport"
path_grouping_policy "group_by_prio"
path_checker "rdac"
features "0"
hardware_handler "1 rdac"
prio "rdac"
failback immediate
rr_weight "uniform"
no_path_retry "12"
}
}

In CentOS 6.x when you restart multipathd or restart server, using

multipathd -k
multipathd> show config
multipathd> exit


That prints out the build-in defaults. See

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/pdf/DM_Multipath/Red_Hat_Enterprise_Linux-7-DM_Multipath-en-US.pdf

chapter 4.


in output you see your particular configuration instead than the default
one for this particular device.
In CentOS 7.3 instead I see it two times, the first one with the default
built-in values (eg "no_path_retry   fail") and at the end the customized
one.
So it is not clear what is the actual configuration that device mapper
multipath is using...
The last wins?
Is this expected behaviour? In that case what command can I use to
crosscheck it (apart from real testing that is anyway necessary to verify
too)?
Eg in CentOS 7.3 I'm using device-mapper-multipath-0.4.9-99.el7_3.1.x86_64
while on CentOS 6.8 I'm using device-mapper-multipath-0.4.9-93.el6.x86_64

Thanks in advance,
Gianluca


To configure a custom setup and enable it please see chapter 3 of the 
RHEL documentation about device-mapper multipath.


Regards

Alexander




___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] time zone

[TE Dukes]

-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard
Sent: Tuesday, January 31, 2017 4:44 PM
To: CentOS mailing list
Subject: Re: [CentOS] time zone



> Date: Tuesday, January 31, 2017 16:02:37 -0500
> From: TE Dukes 
>
> Today, I started getting this error when trying to login to
> zoneminder:
> 
> ZoneMinder is not installed properly: php's date.timezone is not set 
> to a valid timezone
> 
> Zoneminder has been running since last Wednesday when I installed it. 
> Today, I get this.
> 
> In /etc/php.ini, I have date.timezone = America/New_York, which I 
> added when zoneminder was installed.
> 
> Output from date: Tue Jan 31 15:56:26 EST 2017
> 
> Output from ll /etc/localtime: lrwxrwxrwx. 1 root root 38 Jan 25
> 19:05 /etc/localtime -> ../usr/share/zoneinfo/America/New_York
>  
> Been searching for hours for another file that may be overriding 
> php.ini
> 

Put a simple php page on your/the server (where zoneminder is
running) with the "phpinfo()" function, and then look at the timezone
information in the "date" section of the output. 

If it isn't showing the correct value, check the location of the php.ini
that is being used in the "Loaded Configuration File" value toward the top
of that output.

By default, php doesn't use the system's TZ,


Hello,

I did, it shows the error about not being correctly set:

Warning: phpinfo(): It is not safe to rely on the system's timezone
settings. You are *required* to use the date.timezone setting or the
date_default_timezone_set() function. In case you used any of those methods
and you are still getting this warning, you most likely misspelled the
timezone identifier. We selected the timezone 'UTC' for now, but please set
date.timezone to select your timezone. in /var/www/html/phpinfo.php on line
4

Why would it just start doing this?



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] multipath show config different in CentOS 7?

[Gianluca Cecchi]

Hello,
suppose I want to use a special configuration for my IBM/1814 storage array
luns, then I put something like this in multipath.conf

devices {
device {
vendor "IBM"
product "^1814"
product_blacklist "Universal Xport"
path_grouping_policy "group_by_prio"
path_checker "rdac"
features "0"
hardware_handler "1 rdac"
prio "rdac"
failback immediate
rr_weight "uniform"
no_path_retry "12"
}
}

In CentOS 6.x when you restart multipathd or restart server, using

multipathd -k
multipathd> show config
multipathd> exit

in output you see your particular configuration instead than the default
one for this particular device.
In CentOS 7.3 instead I see it two times, the first one with the default
built-in values (eg "no_path_retry   fail") and at the end the customized
one.
So it is not clear what is the actual configuration that device mapper
multipath is using...
The last wins?
Is this expected behaviour? In that case what command can I use to
crosscheck it (apart from real testing that is anyway necessary to verify
too)?
Eg in CentOS 7.3 I'm using device-mapper-multipath-0.4.9-99.el7_3.1.x86_64
while on CentOS 6.8 I'm using device-mapper-multipath-0.4.9-93.el6.x86_64

Thanks in advance,
Gianluca
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] time zone

[Richard]

> Date: Tuesday, January 31, 2017 16:02:37 -0500
> From: TE Dukes 
>
> Today, I started getting this error when trying to login to
> zoneminder:
> 
> ZoneMinder is not installed properly: php's date.timezone is not
> set to a valid timezone
> 
> Zoneminder has been running since last Wednesday when I installed
> it. Today, I get this.
> 
> In /etc/php.ini, I have date.timezone = America/New_York, which I
> added when zoneminder was installed.
> 
> Output from date: Tue Jan 31 15:56:26 EST 2017
> 
> Output from ll /etc/localtime: lrwxrwxrwx. 1 root root 38 Jan 25
> 19:05 /etc/localtime -> ../usr/share/zoneinfo/America/New_York
>  
> Been searching for hours for another file that may be overriding
> php.ini
> 

Put a simple php page on your/the server (where zoneminder is
running) with the "phpinfo()" function, and then look at the timezone
information in the "date" section of the output. 

If it isn't showing the correct value, check the location of the
php.ini that is being used in the "Loaded Configuration File" value
toward the top of that output.

By default, php doesn't use the system's TZ,




___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] time zone

[TE Dukes]

Today, I started getting this error when trying to login to zoneminder:

 

ZoneMinder is not installed properly: php's date.timezone is not set to a
valid timezone

 

Zoneminder has been running since last Wednesday when I installed it. Today,
I get this.

 

In /etc/php.ini, I have date.timezone = America/New_York, which I added when
zoneminder was installed.

 

Output from date: Tue Jan 31 15:56:26 EST 2017

 

Output from ll /etc/localtime: lrwxrwxrwx. 1 root root 38 Jan 25 19:05
/etc/localtime -> ../usr/share/zoneinfo/America/New_York

 

Been searching for hours for another file that may be overriding php.ini

 

TIA

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Question about 7.3

[Johnny Hughes]

On 01/30/2017 07:41 PM, TE Dukes wrote:
> I haven't done a fresh install in years. I've always gone the upgrade route.
> Seemed to have always worked for me.
> 
> I moved to 7.3 since it supports the latest versions of some programs I want
> to use to implement as a backup server/RAID/NAS for 3 machines here at home
> and a remote laptop at work.
> 
> So, the question is, is there something different in 7.3 than the previous 7
> versions?
> 
> The reason I ask is I was running a lesser version of 7, I think 7.1, as a
> VM on 6.8. I remember I chose not to install the most recent version at the
> time. Never had these issues. Not really issues but everything just worked
> without a lot of expertise involved.
> 
> One thing I could never figure out is that on 6.8, I have the zoneminder
> repo installed and when I did a yum update on the 7.1 VM, it was also
> accessing the zmrepo which wasn't installed. Just thought it was odd.
> 
> Anyway, I really appreciate the help and keep paying it forward!!

If you do a yum update after install from any CentOS-7 install and if
you choose to accept the updates then you are running the latest version
of CentOS-7 (right now, 7.3.1611 + updates).

CentOS-7 is the distro .. 7.0.1406, 7.1.1501, 7.2.1511, 7.3.1611 are
'point in time' releases of CentOS-7 .. the 14, 15 or 16 is the YEAR
that Red Hat released the source code (2015 or 2016).  The last two
digits are the MONTH that Red Hat released that version of the Source
Code.  So, 7.0.1406 is based on the Source Code for RHEL 7.0 and was
released in June of 2014.  The latest point in time release is 7.3.1611
.. It is based on RHEL 7.3 Source Code, which was released in November
of 2016.

So, if you install 7.0.1406, then run yum update, you will be at 7.3.1611.

If you want to know what version you are actually running do:

cat /etc/centos-release

It will look something like this:

[jhughes@w541 ~]$ cat /etc/centos-release
CentOS Linux release 7.3.1611 (Core)

NOTE:  If you are NOT running 7.3.1611 then your install is insecure.
In order to keep you CentOS install secure, you must maintain it up to
date by running 'yum update' periodically.

This mailing list gets all mail daily forwarded as a digest from the
centos-announce mailing list which lists updates.  Here is an archive:

https://lists.centos.org/pipermail/centos-announce/

Since 7.1.1503 source code was released in March 2015, your install
would be missing all the updates listed there for 'CentOS 7' after March
2015 .. and also all updates listed on or after March 2105 on the CR
announce list as well:

https://lists.centos.org/pipermail/centos-cr-announce/

So your machine would be vulnerable to any update that is listed as
'security' in those months (including and after) March 2015, if you have
not done updates.  If you have done updates often, then you are running
7.3.1611.

Thanks,
Johnny Hughes




signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS-announce Digest, Vol 143, Issue 12

[centos-announce-request]

Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. Release for CentOS AltArch 7 (1611) on i386   Architecture
  (Johnny Hughes)


--

Message: 1
Date: Mon, 30 Jan 2017 07:24:20 -0600
From: Johnny Hughes 
To: CentOS-Announce 
Subject: [CentOS-announce] Release for CentOS AltArch 7 (1611) on i386
Architecture
Message-ID: <7a4903a6-8535-0cb4-a2ed-19c66b61e...@centos.org>
Content-Type: text/plain; charset="utf-8"

The CentOS AltArch SIG is a group of people working to build alternative
architecture support derived from CentOS Linux's sources. You can find
more details about the AltArch group at:

https://wiki.centos.org/SpecialInterestGroup/AltArch

Including details on how to get involved and ways to get help for
architecture specific issues.

This is the release announcement for the i386 (Intel 32-bit)
Architecture based on the source code released for CentOS-7 (1611).  It
includes all packages that build on x86 32-bit processors.

The release notes for the normal CentOS-7 apply:

https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7

with the following notes that are specific to i386:

https://wiki.centos.org/SpecialInterestGroup/AltArch/i386

If you already have a previous version of CentOS-7 i386 installed, just
running 'yum update' will get you the latest packages installed.

ISOs can be downloaded from:

http://mirror.centos.org/altarch/7/isos/i386/

Here are the SHA256SUMS for the ISOs:

CentOS-7-i386-DVD-1611.iso:
25eff443460d53155cb837983c947fb3d74f4c0a3077dc699c7d50e9fdb4c0f3 

CentOS-7-i386-Everything-1611.iso
578a475248ecef427269357b7ff22b973a007f534988f39f365b8dded43fad72 

CentOS-7-i386-LiveGNOME-1611.iso:
16a75041a77e4d98922d2f68c54abef35f50a1e8aa863f182ab84b443cb0fcd1 

CentOS-7-i386-LiveKDE-1611.iso:
f9651851adee59d646b509757186f038f2b453d285d92dce5b7b91c396d20d1a 

CentOS-7-i386-Minimal-1611.iso:
bf0e17041aad294fbb3fa5c6fb100258ace4f62b94d5bf3356b40f9807a88805 

CentOS-7-i386-NetInstall-1611.iso:
249c344d3e82f49be3195e06741276f409815b1d4785f1439fc47c342eb6dd7c 

===

The CentOS team will have a Dojo in Brussels, Belgium on Friday 3th
February 2017:

https://wiki.centos.org/Events/Dojo/Brussels2017

I will be at the Dojo to discuss the i386 distribution with those who
are interested.  I will also be at the CentOS Booth at FOSDEM 2017 (
https://fosdem.org/2017/ ) in Brussels, Belgium on February 4th and 5th,
2017.  I will also attend the Config Management Camp EU (
http://cfgmgmtcamp.eu/ ) in Ghent, Belgium on the 6th of February,
2017.  If you have any questions and will be at any of those locations,
please look me up.

Bug reports and feedback about specific packages should be filed at
https://bugs.centos.org/ against the relevant package name, for project
CentOS Linux 7, in the same manner as you would for x86_64. However, do
mention the architecture as applicable.

===

Johnny Hughes
CentOS-7 i386 AltArch Maintainer
Twitter:  @JohnnyCentOS
Freenode IRC:  hughesjr


-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: 


--

Subject: Digest Footer

___
CentOS-announce mailing list
centos-annou...@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce


--

End of CentOS-announce Digest, Vol 143, Issue 12

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] NIC Stability Problems Under Xen 4.4 / CentOS 6 / Linux 3.18

[Jinesh Choksi]

On 30 January 2017 at 22:17, Adi Pircalabu  wrote:

> May I chip in here? In our environment we're randomly seeing:
>
> Jan 17 23:40:14 xen01 kernel: ixgbe :04:00.1 eth6: Detected Tx Unit
> Hang
>

Someone in this thread: https://sourceforge.net/p/e1000/bugs/530/#2855
 reported that *"With these kernels I was only able to work around the
issue by disabling tx-checksumming offload with ethtool."*

However, that was reported for Kernels 4.2.6 / 4.2.8 / 4.4.8 and 4.4.10. I
just thought it could be something you could rule out and hence mentioned
it:

ethtool --offload eth6 rx off tx off


Another thing to rule out in case its a regression with Intel NICs and TSO:

# tso => tcp-segmentation-offload
# gso => generic-segmentation-offload
# gro => generic-receive-offload
# sg => scatter-gather
# ufo => udp-fragmentation-offload (Cannot change)
# lro => large-receive-offload (Cannot change)

ethtool -K eth6 tso off gso off gro off sg off
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] [Fwd: The CentOS list]

[Tony Mountifield]

In article <37213.128.135.52.6.1485815997.squir...@cosmo.uchicago.edu>,
Valeri Galtsev  wrote:
> Dear All,
> 
> Mark has problem sending mail to centos@centos.org list... He has trouble
> with flash plugin on CentOS 6, please, take a look at his e-mail below.
> I'll try to see what I can do to help, but what I can do definitely is no
> match to Experts on this list.
> 
> Thanks in advance!
> 
> Valeri

Mark's original message asking about flash-plugin did eventually show up,
as I'm sure people have seen by now.

Looking at its Received headers, it appears it got stuck for 5 hours at
Mark's email provider. It was submitted to host290.hostmonster.com using
squirrelmail at 18:56 GMT, but didn't leave that machine for the next hop
(cmgw2) until 23:55 GMT.

Hope this helps!
Cheers
Tony

>  Original Message 
> Subject: The CentOS list
> From:m.r...@5-cent.us
> Date:Mon, January 30, 2017 3:11 pm
> To:  "Valeri Galtsev" 
> --
> 
> Hi, Valeri,
> 
>I've tried, twice, to post to the list today, and they neither show up,
> *nor* do I get a blocked message - they just go to /dev/null.
> 
>The second was just a test, the first was asking if anyone else was
> seeing, with CentOS 6 (updated) flash-plugin crashing every 10-15 min.
> And there's no downgrade for it.
> 
>mark

-- 
Tony Mountifield
Work: t...@softins.co.uk - http://www.softins.co.uk
Play: t...@mountifield.org - http://tony.mountifield.org
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Question about 7.3

[Götz Reinicke]

> Am 31.01.2017 um 02:41 schrieb TE Dukes :
> 
> I haven't done a fresh install in years. I've always gone the upgrade route.
> Seemed to have always worked for me.
> 
> I moved to 7.3 since it supports the latest versions of some programs I want
> to use to implement as a backup server/RAID/NAS for 3 machines here at home
> and a remote laptop at work.
> 
> So, the question is, is there something different in 7.3 than the previous 7
> versions?

Have a look:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.3_Release_Notes/index.html
 


> 
> The reason I ask is I was running a lesser version of 7, I think 7.1, as a
> VM on 6.8. I remember I chose not to install the most recent version at the
> time. Never had these issues. Not really issues but everything just worked
> without a lot of expertise involved.
> 
> One thing I could never figure out is that on 6.8, I have the zoneminder
> repo installed and when I did a yum update on the 7.1 VM, it was also
> accessing the zmrepo which wasn't installed. Just thought it was odd.
> 
> Anyway, I really appreciate the help and keep paying it forward!

So your question is, why your Centos 7.x VM is accessing the same repository as 
your 6.x Installation you upgraded from?

If you did an upgrade 6.x to 7.x it keeps the settings for the repos I guess.

Regards . Götz
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos