As we are getting closer to the 0.4 release, we already finished 3
release candidates, and rc4 is fairly close to 0.4
If anyone is interested in trying out, feedback is highly appreciated!
Full changelog at http://theforeman.org/versions/show/13
RPM is available in our test repository, note that if you are using a
smart proxy, you would need to update it too.
> For mysql I had to update my.cnf in order for the the report expire to
> work. "rake reports:expire"
>
> I was getting this error with foreman 0.4rc4
>
> # rake reports:expire days=30 RAILS_ENV="production"
> (in /opt/foreman)
> rake aborted!
> Mysql::Error: Got a packet bigger than 'max_allowed_packet' bytes:
> SELECT id FROM reports WHERE (reports.id IN
>
>
> I add this line to my.cnf and restarted mysql
> max_allowed_packet=32M
>
thanks, any chance you can document it in the wiki?
sh-3.2# RAILS_ENV=production rake db:migrate
(in /opt/comcast/platform/foreman/foreman)
== CreateHosts: migrating
···
====================================================
rake aborted!
An error has occurred, all later migrations canceled:
Mysql2::Error: BLOB/TEXT column ‘title’ used in key specification
without a key length: CREATE INDEX index_resources_on_title_and_restype ON resources (title, restype)
(See full trace by running task with --trace)
sh-3.2#
(in /opt/foreman)
rake aborted!
Mysql::Error: Got a packet bigger than ‘max_allowed_packet’ bytes:
SELECT id FROM reports WHERE (reports.id IN
I add this line to my.cnf and restarted mysql
max_allowed_packet=32M
thanks, any chance you can document it in the wiki?
–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group athttp://groups.google.com/group/foreman-users?hl=en.
···
On Tue, Nov 22, 2011 at 11:53 PM, Telmo wrote:
> I am getting
>
> sh-3.2# RAILS_ENV=production rake db:migrate
> (in /opt/comcast/platform/foreman/foreman)
> == CreateHosts: migrating
> ====================================================
> rake aborted!
> An error has occurred, all later migrations canceled:
>
> Mysql2::Error: BLOB/TEXT column 'title' used in key specification
> without a key length: CREATE INDEX
> `index_resources_on_title_and_restype` ON `resources` (`title`,
> `restype`)
>
> (See full trace by running task with --trace)
> sh-3.2#
>
> On Oct 26, 7:46 am, Ohad Levy wrote:
>> On Wed, Oct 26, 2011 at 2:10 PM, Chuck wrote:
>> > For mysql I had to update my.cnf in order for the the report expire to
>> > work. "rake reports:expire"
>>
>> > I was getting this error with foreman 0.4rc4
>>
>> > # rake reports:expire days=30 RAILS_ENV="production"
>> > (in /opt/foreman)
>> > rake aborted!
>> > Mysql::Error: Got a packet bigger than 'max_allowed_packet' bytes:
>> > SELECT id FROM `reports` WHERE (`reports`.`id` IN
>>
>> > I add this line to my.cnf and restarted mysql
>> > max_allowed_packet=32M
>>
>> thanks, any chance you can document it in the wiki?
>>
>>
>>
>>
>>
>>
>>
>> > --
>> > You received this message because you are subscribed to the Google Groups "Foreman users" group.
>> > To post to this group, send email to foreman-users@googlegroups.com.
>> > To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
>> > For more options, visit this group athttp://groups.google.com/group/foreman-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups "Foreman users" group.
> To post to this group, send email to foreman-users@googlegroups.com.
> To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.
>
>